Re: [gentoo-portage-dev] Releasing portage-2.2.8
Am 09.12.2013 16:44, schrieb Brian Dolbec: > On Mon, 2013-12-09 at 14:56 +0100, Sebastian Luther wrote: >> Hi all, >> >> I'd like to release a new portage version. You may find the list >> of fixed bugs on the tracker [1] (those not marked as fixed). >> >> Most notable are the slot operator related fixes and the fix for >> binary packages with respect to use dependencies on USE_EXPAND >> values. >> >> I don't think there's anything that should go into the NEWS >> file. >> >> Any objections? >> >> >> What is then needed is someone to create the tarball using >> mkrelease.sh and upload it somewhere. >> >> The ebuild needs an updated SRC_URI. >> >> Any Volunteers? >> >> >> [1] https://bugs.gentoo.org/484436 >> > > Yeah, we also need to update the ebuild. 2.2.7 was still using the > now deprecated EAPI 2 which was getting the attention from the > stabilizing devs. I think it is time to update the ebuild eapi. > We can always keep 2.2.7 around for an upgrade path from older > eapi's. I haven't looked at the upgrade path for quite a while, but it was usually a pain when portage changed its EAPI or python deps. While it's true that leaving old ebuilds available helps with that, it's still annoying. So if we do this, we should have a real good reason. The council voted that EAPI 1 and 2 are discouraged. I'd argue that minimizing upgrade hassle is more worth than not using a discouraged EAPI. To summarize: leave it as is. > > Mike, what about Sebastian's last patch about the /var/run and > compny. The email I fail to find at the moment. I know there was > some additional comments on the bug about /var/lib and one other > directory being excluded. >
Re: [gentoo-portage-dev] Releasing portage-2.2.8
On Mon, 2013-12-09 at 14:56 +0100, Sebastian Luther wrote: > Hi all, > > I'd like to release a new portage version. You may find the list of > fixed bugs on the tracker [1] (those not marked as fixed). > > Most notable are the slot operator related fixes and the fix for binary > packages with respect to use dependencies on USE_EXPAND values. > > I don't think there's anything that should go into the NEWS file. > > Any objections? > > > What is then needed is someone to create the tarball using mkrelease.sh > and upload it somewhere. > > The ebuild needs an updated SRC_URI. > > Any Volunteers? > > > [1] https://bugs.gentoo.org/484436 > Yeah, we also need to update the ebuild. 2.2.7 was still using the now deprecated EAPI 2 which was getting the attention from the stabilizing devs. I think it is time to update the ebuild eapi. We can always keep 2.2.7 around for an upgrade path from older eapi's. Mike, what about Sebastian's last patch about the /var/run and compny. The email I fail to find at the moment. I know there was some additional comments on the bug about /var/lib and one other directory being excluded. signature.asc Description: This is a digitally signed message part
[gentoo-portage-dev] Releasing portage-2.2.8
Hi all, I'd like to release a new portage version. You may find the list of fixed bugs on the tracker [1] (those not marked as fixed). Most notable are the slot operator related fixes and the fix for binary packages with respect to use dependencies on USE_EXPAND values. I don't think there's anything that should go into the NEWS file. Any objections? What is then needed is someone to create the tarball using mkrelease.sh and upload it somewhere. The ebuild needs an updated SRC_URI. Any Volunteers? [1] https://bugs.gentoo.org/484436
