Re: [gentoo-portage-dev] New portage version with latest fixes in git is needed
On Sat, 2014-01-04 at 15:28 +0100, Pacho Ramos wrote: Hello I think this was pointed some days ago, but would be nice (and needed) to get a newer portage version including fixes from git, some of them important like: https://bugs.gentoo.org/show_bug.cgi?id=490362 Not sure if I can contribute with something on this, but if you thing so, please let me know Thanks! Yes, I planned to get it out this weekend, if all goes well. There are one or two more patches to apply. Then I'll start packaging it. Is everyone else in agreement? signature.asc Description: This is a digitally signed message part
Re: [gentoo-portage-dev] New portage version with latest fixes in git is needed
Am 04.01.2014 16:03, schrieb Mike Frysinger: On Saturday 04 January 2014 09:56:28 Brian Dolbec wrote: On Sat, 2014-01-04 at 15:28 +0100, Pacho Ramos wrote: I think this was pointed some days ago, but would be nice (and needed) to get a newer portage version including fixes from git, some of them important like: https://bugs.gentoo.org/show_bug.cgi?id=490362 Not sure if I can contribute with something on this, but if you thing so, please let me know Yes, I planned to get it out this weekend, if all goes well. There are one or two more patches to apply. Then I'll start packaging it. Is everyone else in agreement? we should document the release process. ideally, it should be as simple as: make dist PV=2.1.8 and even: make distcheck PV=2.1.8 -mike There is mkrelease.sh in the portage repo. The following commands creates a portage-2.2.7.tar.bz2 that's almost identical to the one released by Zac (Changelog differs): $ ./mkrelease.sh --changelog-rev v2.2.6 -t 2.2.7 2.2.7 The first argument states where the Changelog entries should begin (tag v2.2.6 in this case). The second argument is the tag to create the tarball from. The third argument is the new version. I don't know how Zac choose the --changelog-rev parameter. That's why the Changelog is different. For 2.2.8 the process should look like: * Create a tag named v2.2.8. * ./mkrelease.sh --changelog-rev -t 2.2.8 2.2.8 * Upload the tarball somewhere * Copy the ebuild (adjust SRC_URI) Sebastian
Re: [gentoo-portage-dev] New portage version with latest fixes in git is needed
Am 04.01.2014 15:56, schrieb Brian Dolbec: On Sat, 2014-01-04 at 15:28 +0100, Pacho Ramos wrote: Hello I think this was pointed some days ago, but would be nice (and needed) to get a newer portage version including fixes from git, some of them important like: https://bugs.gentoo.org/show_bug.cgi?id=490362 Not sure if I can contribute with something on this, but if you thing so, please let me know Thanks! Yes, I planned to get it out this weekend, if all goes well. There are one or two more patches to apply. Then I'll start packaging it. I'd say, apply only the really necessary patches (i.e. the python-2.6 compat patch) and commit the remaining patches after the release. Is everyone else in agreement? Go for it. Sebastian
