blob: f050f5f5c2247304c84369e42a6ee8935b65ae1e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
OVERVIEW
The CVS module 'gentoolkit' contains all the scripts and stuff for both the
gentoolkit and the gentoolkit-dev package. The gentoolkit-dev package is
an optional add-on, that is only intented for the Gentoo developers.
STYLE POLICY
If you're touching any of the python scripts please don't change the indentation
style (if it's using tabs, you should use tabs too). Especially don't mix
spaces and tabs as that makes the code completely unreadable.
MAKING A RELEASE
Releases should only be made by members of the tools-portage team. See
http://www.gentoo.org/proj/en/metastructure/herds/herds.xml?select=tools-portage
for who to contact on IRC, or shuffle over a bug report to us, or send
us a mail at tools-portage@gentoo.org if you need an immediate release.
The release manager (big words;) will then do
1) make VERSION=major.minor.patch RELEASE_TAG=<optional> dist-gentoolkit
2) copy dist/gentoolkit-${VERSION}-${RELEASE_TAG}.tar.gz to
emu.gentoo.org/space/distfiles-local/
3) make a new ebuild, app-portage/gentoolkit/gentoolkit-${VERSION}.ebuild
with a SRC_URI that points to
mirror://gentoo/gentoolkit-${VERSION}-${RELEASE_TAG}.tar.gz
(just use one of the previous ebuilds)
The process is similar for gentoolkit-dev:
1) make dist-gentoolkit-dev
2) copy dist/gentoolkit-dev-${VERSION}-${RELEASE_TAG}.tar.gz to emu
3) update app-portage/gentoolkit-dev
Important!
1) _ALWAYS_ make sure you don't "overwrite" a previous release. Your
new VERSION must be newer than any previous released version. If you
mess up a release, don't overwrite with the same release number, iterate
the patch version and try again (and again, and again until you get
it right;)
|
