Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@g.o
Subject: [gentoo-portage-dev] [RFC] trigger to stop Manifest1 generation (bug #167667)
Date: Tue, 20 Feb 2007 22:11:39
Message-Id: 45DB71E8.9080806@gentoo.org
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 http://bugs.gentoo.org/show_bug.cgi?id=167667
5
6 In order so smoothly and transparently drop Manifest1, it seems like
7 we'll need a toggle built into portage so that it automatically
8 drops Manifest1 when appropriate. The need for this toggle will be
9 critical when we make the move to drop Manifest1 from the gentoo-x86
10 cvs tree.
11
12 Please review the attached patch for bug #167667 which triggers the
13 dropping of Manifest1 via an empty file named
14 "${PORTDIR}/manifest1_obsolete". The file is repo/overlay specific,
15 so various overlays can keep or drop Manifest1 depending on whether
16 that file has been added to the overlay.
17
18 In order to drop manifest1 from cvs, we will also nned to add
19 support to repoman so that it handles Manifest1 digest files
20 correctly. Perhaps it should automatically remove them from cvs?
21
22 Zac
23 -----BEGIN PGP SIGNATURE-----
24 Version: GnuPG v2.0.2 (GNU/Linux)
25
26 iD8DBQFF23Hm/ejvha5XGaMRAvZfAKDLiQdrEmuBz5OykDvSTfqBxDqUuwCeIcYR
27 J7MbsD0Ac9jcqm13nv3ujT0=
28 =H2Vb
29 -----END PGP SIGNATURE-----

Attachments

File name MIME type
digestgen.patch text/plain