1 |
Am 04.01.2014 16:03, schrieb Mike Frysinger: |
2 |
> On Saturday 04 January 2014 09:56:28 Brian Dolbec wrote: |
3 |
>> On Sat, 2014-01-04 at 15:28 +0100, Pacho Ramos wrote: |
4 |
>>> I think this was pointed some days ago, but would be nice (and |
5 |
>>> needed) to get a newer portage version including fixes from |
6 |
>>> git, some of them important like: |
7 |
>>> https://bugs.gentoo.org/show_bug.cgi?id=490362 |
8 |
>>> |
9 |
>>> Not sure if I can contribute with something on this, but if you |
10 |
>>> thing so, please let me know |
11 |
>> |
12 |
>> Yes, I planned to get it out this weekend, if all goes well. |
13 |
>> |
14 |
>> There are one or two more patches to apply. Then I'll start |
15 |
>> packaging it. |
16 |
>> |
17 |
>> Is everyone else in agreement? |
18 |
> |
19 |
> we should document the release process. ideally, it should be as |
20 |
> simple as: make dist PV=2.1.8 |
21 |
> |
22 |
> and even: make distcheck PV=2.1.8 -mike |
23 |
> |
24 |
|
25 |
There is mkrelease.sh in the portage repo. |
26 |
|
27 |
The following commands creates a portage-2.2.7.tar.bz2 that's almost |
28 |
identical to the one released by Zac (Changelog differs): |
29 |
|
30 |
$ ./mkrelease.sh --changelog-rev v2.2.6 -t 2.2.7 2.2.7 |
31 |
|
32 |
The first argument states where the Changelog entries should begin |
33 |
(tag v2.2.6 in this case). |
34 |
The second argument is the tag to create the tarball from. |
35 |
The third argument is the new version. |
36 |
|
37 |
I don't know how Zac choose the --changelog-rev parameter. That's why |
38 |
the Changelog is different. |
39 |
|
40 |
For 2.2.8 the process should look like: |
41 |
* Create a tag named v2.2.8. |
42 |
* ./mkrelease.sh --changelog-rev ???? -t 2.2.8 2.2.8 |
43 |
* Upload the tarball somewhere |
44 |
* Copy the ebuild (adjust SRC_URI) |
45 |
|
46 |
|
47 |
Sebastian |