From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1ENGZr-0000Xs-5F for garchives@archives.gentoo.org; Wed, 05 Oct 2005 21:13:27 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id j95L4SAA031969; Wed, 5 Oct 2005 21:04:28 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id j95L4RQO011546 for ; Wed, 5 Oct 2005 21:04:27 GMT Received: from cpe-65-26-255-237.wi.res.rr.com ([65.26.255.237] helo=nightcrawler) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1ENGZN-0006T5-EW for gentoo-portage-dev@lists.gentoo.org; Wed, 05 Oct 2005 21:12:57 +0000 Date: Wed, 5 Oct 2005 16:13:06 -0500 From: Brian Harring To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] Questions about CVS locations and GID... Message-ID: <20051005211306.GE10159@nightcrawler> References: <43443257.8090800@egr.msu.edu> <20051005202429.GC10159@nightcrawler> <20051005215703.73327655@snowdrop.home> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LSp5EJdfMPwZcMS1" Content-Disposition: inline In-Reply-To: <20051005215703.73327655@snowdrop.home> User-Agent: Mutt/1.5.8i X-Archives-Salt: d31632dd-823b-41cd-b588-a3a5f4f60123 X-Archives-Hash: eb4d86df5f12375754f362282b030b81 --LSp5EJdfMPwZcMS1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 05, 2005 at 09:57:03PM +0100, Ciaran McCreesh wrote: > On Wed, 5 Oct 2005 15:24:29 -0500 Brian Harring > wrote: > | To head off the "it's not going to work for vim-*", yah, you'll be=20 > | boned and have to install duplicate vim-* into the global prefix. > | Bluntly, either you dive in and start wading through the problems=20 > | (fixing them as you go), or you sit back listening to how it's never=20 > | going to work (thus accomplishing nothing). >=20 > It can be made to work, so long as you don't a) jump in without proper > planning, b) assume that you'll not have to modify ebuilds and c) > demand that as soon as it's available, it works for all ebuilds. I'd point out that the last time prefix was brought up, all of those=20 points were addressed. A) would like to hear what you think is required planning wise=20 compared to the previous haubi prototype patch. B) Modifying the ebuilds is required, although modifying the underlying=20 base defaults does cover a good swath of ebuilds C) See previous comments from last round of this stating "those who=20 want it, have to do the work". ~harring --LSp5EJdfMPwZcMS1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDREHivdBxRoA3VU0RAsaiAJ0d39R+kEWIsO4cI5Ut/7JoU74vswCguigE V0tWQDbYX+c5NN4NwCuT/bc= =sufz -----END PGP SIGNATURE----- --LSp5EJdfMPwZcMS1-- -- gentoo-portage-dev@gentoo.org mailing list