From ae60b4b979ee95fc7e7899f12b200b490d05cd4d Mon Sep 17 00:00:00 2001 From: karltk Date: Wed, 7 Jan 2004 12:21:21 +0000 Subject: New build system svn path=/; revision=47 --- trunk/README.Developer | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 trunk/README.Developer (limited to 'trunk/README.Developer') diff --git a/trunk/README.Developer b/trunk/README.Developer new file mode 100644 index 0000000..6a98832 --- /dev/null +++ b/trunk/README.Developer @@ -0,0 +1,37 @@ + +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. + +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= 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;) + -- cgit v1.2.3