From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpauth03.mail.atl.earthlink.net (smtpauth03.mail.atl.earthlink.net [209.86.89.63]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j447HeOi023586 for ; Wed, 4 May 2005 07:17:40 GMT Received: from [64.166.167.20] (helo=sarge.electronerdia.net) by smtpauth03.mail.atl.earthlink.net with asmtp (Exim 4.34) id 1DTE8d-0004Jn-M3 for gentoo-dev@lists.gentoo.org; Wed, 04 May 2005 03:17:43 -0400 Received: from sheila.electronerdia.net (sheila.electronerdia.net [192.168.1.32]) by sarge.electronerdia.net (Postfix) with ESMTP id 3EC913C4608 for ; Wed, 4 May 2005 00:13:49 -0700 (PDT) From: John Myers To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Cutting down on non-cascaded profiles Date: Wed, 4 May 2005 00:17:40 -0700 User-Agent: KMail/1.8 References: <4274ACD1.9020003@gentoo.org> <1115136614.889.281.camel@cgianelloni.nuvox.net> In-Reply-To: <1115136614.889.281.camel@cgianelloni.nuvox.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1293705.iEATjgS7gn"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200505040017.41237.electronerd@monolith3d.com> X-ELNK-Trace: 8839a2c17b2169aa1aa676d7e74259b7b3291a7d08dfec7914b5458ec9f348b8fc2bb3063d1c1942350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 64.166.167.20 X-Archives-Salt: 191c4267-2b31-49a3-bbbf-0d36a9cac066 X-Archives-Hash: 616834f3935f8e8408d06cebcac9d88d --nextPart1293705.iEATjgS7gn Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 03 May 2005 09:10, Chris Gianelloni wrote: > I think an easier solution would be a portage rescue set of profiles. > These would be minimal profiles not designed for actual use, but only > for performing a portage update for those people that lag too far > behind. The idea would be a very tiny profile, per arch, that is not > cascaded. Perhaps another solution would be to create a system with archives of the=20 profiles and packages necessary to do an upgrade from an old portage and=20 profile to a new portage and profile, seeing as portage has circular=20 effective dependencies on at least the tree and python, perhaps other stuff= =20 as well. This could be some sort of script which downloads the archive, the= n=20 upgrades, one major shift at a time. Once said system is in place, notices could be put in the deprecated files= =20 (and of course the homepage) to that effect, and the old profiles removed=20 from the main tree after a while. Just a thought. =2D-electronerd --nextPart1293705.iEATjgS7gn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux) iD8DBQBCeHcVvqDgVb4O7CURAuHrAKCWq7I3TBcYqQWq1Wt3HA1V2EW7hQCeKR5k zCam9yuw3tmqPK2RtF36KMc= =TVf+ -----END PGP SIGNATURE----- --nextPart1293705.iEATjgS7gn-- -- gentoo-dev@gentoo.org mailing list