[gentoo-dev] EAPI-3 times and dates
EAPI-3 was approved by the council during their last meeting (2010-01-18). Which portage versions do support it? (I wasn't able to find it in the docs.) When can we stabilize EAPI-3 ebuilds? (I guess this is again a council decision?) How long do we have to provide ebuilds for older EAPIs? (We can drop them as long as users are able to upgrade to an EAPI-3 capable package-manager for at least one year from now/after stabilisation?) Is this worth to be documented if it isn't?
[gentoo-dev] Usage of vecho in the tree
A number of ebuilds use vecho from portage.
But vecho is not defined in general. It's a portage internal command.
Do we want to fix the ebuilds? Add a repoman check so we don't have to clean
them regularly?
Or do we want to provide it via profiles/base/profile.bashrc like elog?
BTW: Do we want to remove the elog check from the profiles now?
./dev-scheme/bigloo/bigloo-3.2b_p2.ebuild: vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-scheme/elk/elk-3.99.7.ebuild: vecho Tests already run
during compile
./mail-mta/courier/courier-0.61.2.ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./mail-mta/courier/courier-0.59.0.ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./mail-mta/courier/courier-0.60.0.ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./mail-mta/courier/courier-0.61.1.ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./dev-libs/libmemcached/libmemcached-0.30.ebuild:vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-libs/libmemcached/libmemcached-0.30.ebuild:vecho Test phase [none]:
${CATEGORY}/${PF}
./dev-libs/libmemcached/libmemcached-0.28.ebuild:vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-libs/libmemcached/libmemcached-0.28.ebuild:vecho Test phase [none]:
${CATEGORY}/${PF}
./dev-lang/php/php-5.2.10.ebuild:vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-lang/php/php-5.2.9-r2.ebuild: vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-lang/php/php-5.2.10-r2.ebuild: vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-lang/php/php-5.2.12.ebuild:vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-lang/php/php-5.2.10-r1.ebuild: vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-lang/php/php-5.2.11-r1.ebuild: vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-lang/php/php-5.2.11.ebuild:vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-lang/mono/mono-2.4..ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./dev-lang/mono/mono-1.2.5.1-r1.ebuild: vecho Test phase [check]:
${CATEGORY}/${PF}
./dev-lang/mono/mono-1.2.6-r3.ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./dev-lang/mono/mono-2.4.2.3.ebuild: vecho Test phase [check]:
${CATEGORY}/${PF}
./dev-lang/mono/mono-2.0..ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./dev-lang/mono/mono-.ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./dev-lang/mono/mono-2.0.1-r1.ebuild:vecho Test phase [check]:
${CATEGORY}/${PF}
./sys-devel/clang/clang-2.6-r1.ebuild: vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-python/pysvn/pysvn-1.7.0.ebuild: vecho Test phase [test]:
${CATEGORY}/${PF}
./dev-python/pysvn/pysvn-1.7.0.ebuild: vecho Test phase [none]:
${CATEGORY}/${PF}
Re: [gentoo-dev] EAPI-3 times and dates
On 01/22/2010 10:58 AM, Torsten Veller wrote: EAPI-3 was approved by the council during their last meeting (2010-01-18). Which portage versions do support it? (I wasn't able to find it in the docs.) I haven't heard of a release that would. When can we stabilize EAPI-3 ebuilds? (I guess this is again a council decision?) When a Portage version supporting EAPI-3 is stable. Council can acknowledge at this point. How long do we have to provide ebuilds for older EAPIs? (We can drop them as long as users are able to upgrade to an EAPI-3 capable package-manager for at least one year from now/after stabilisation?) Normally ebuild developers can just use the latest. As you said the only thing that matters is the package manager upgrade path and that only concerns a few packages. Regards, Petteri signature.asc Description: OpenPGP digital signature
[gentoo-dev] Re: Usage of vecho in the tree
* Torsten Veller ml...@veller.net: Or do we want to provide it via profiles/base/profile.bashrc like elog? That wouldn't work as other package managers don't source profile.bashrc.
Re: [gentoo-dev] last rites: games-util/dzip
Am Mittwoch 20 Januar 2010 schrieb Michael Sterrett: You can look at the discussion at http://bugs.gentoo.org/show_bug.cgi?id=288905 but with the last release in 2003 it seems like a pretty dead package. As we seem to have nothing else that can open dzip files and they are used in the wild, I think we should keep it. I committed 2.9-r3 which fixes the zlib issue, I also added a patch for 64 bit support and an ~amd64 keyword. -- Hanno Böck Blog: http://www.hboeck.de/ GPG: 3DBD3B20 Jabber/Mail:ha...@hboeck.de http://schokokeks.org - professional webhosting signature.asc Description: This is a digitally signed message part.
