On 03/04/12 00:11, Pacho Ramos wrote:
El lun, 19-03-2012 a las 10:22 +0100, Pacho Ramos escribió:
Hello
As talked some time ago with Donnie, sci-physics/abinit is hard to
maintain and, then, he would like to lastrite it after moving package to
sci overlay because looks like nobody from sci
# Samuli Suominen ssuomi...@gentoo.org (03 Apr 2012)
# - Still using the obsolete MusicBrainz RDF based database.
# - Incompatible with latest libmp4v2 API.
# Removal in 30 days wrt bug 409257.
media-libs/tunepimp
El mar, 03-04-2012 a las 08:43 +0200, justin escribió:
On 03/04/12 00:11, Pacho Ramos wrote:
El lun, 19-03-2012 a las 10:22 +0100, Pacho Ramos escribió:
Hello
As talked some time ago with Donnie, sci-physics/abinit is hard to
maintain and, then, he would like to lastrite it after moving
python.eclass looks at the USE_PYTHON variable to determine which
python versions to target when building python packages which support
installation for multiple python abis. Having it in the emerge --info
output would be useful for diagnosing python-related bugs.
Any objections?
Hello,
I've been directed here from the bugzilla:
https://bugs.gentoo.org/show_bug.cgi?id=410585
I will copy my bug report from there, so no need to click :)
Currently there are two different flags which pull the same
library (media-libs/libvpx) for the same purpose.
vpx : Enables vp8 codec
Hi,
The ruby team intends to file a stable request for ruby 1.9 in a week or
so. Most packages using ruby use the ruby-ng and ruby-fakegem eclasses
where the RUBY_TARGETS mechanism selectively handles ruby 1.9
compatibility. However, there are also packages depending directly on
dev-lang/ruby,
On Tue, Apr 3, 2012 at 18:10, Mike Gilbert flop...@gentoo.org wrote:
python.eclass looks at the USE_PYTHON variable to determine which
python versions to target when building python packages which support
installation for multiple python abis. Having it in the emerge --info
output would be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/03/2012 05:33 PM, Paweł Rumian wrote:
Hello,
I've been directed here from the bugzilla:
https://bugs.gentoo.org/show_bug.cgi?id=410585 I will copy my bug
report from there, so no need to click :)
Currently there are two different