List Info

Thread: trigger to stop Manifest1 generation (bug #167667)




trigger to stop Manifest1 generation (bug #167667)
country flaguser name
United States
2007-02-20 16:10:48
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

http://
bugs.gentoo.org/show_bug.cgi?id=167667

In order so smoothly and transparently drop Manifest1, it
seems like
we'll need a toggle built into portage so that it
automatically
drops Manifest1 when appropriate.  The need for this toggle
will be
critical when we make the move to drop Manifest1 from the
gentoo-x86
cvs tree.

Please review the attached patch for bug #167667 which
triggers the
dropping of Manifest1 via an empty file named
"$/manifest1_obsolete".  The file is
repo/overlay specific,
so various overlays can keep or drop Manifest1 depending on
whether
that file has been added to the overlay.

In order to drop manifest1 from cvs, we will also nned to
add
support to repoman so that it handles Manifest1 digest
files
correctly.  Perhaps it should automatically remove them from
cvs?

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (GNU/Linux)

iD8DBQFF23Hm/ejvha5XGaMRAvZfAKDLiQdrEmuBz5OykDvSTfqBxDqUuwCe
IcYR
J7MbsD0Ac9jcqm13nv3ujT0=
=H2Vb
-----END PGP SIGNATURE-----

  
[1]

about | contact  Other archives ( Real Estate discussion Medical topics )