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.43) id 1E7L0t-00008X-Az for garchives@archives.gentoo.org; Mon, 22 Aug 2005 22:43:31 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7MMgAGa032078; Mon, 22 Aug 2005 22:42:10 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7MMg9Ye024656 for ; Mon, 22 Aug 2005 22:42:09 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 1E7L0J-0001Tl-7S for gentoo-portage-dev@lists.gentoo.org; Mon, 22 Aug 2005 22:42:55 +0000 Date: Mon, 22 Aug 2005 17:41:47 -0500 From: Brian Harring To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] Environment Whitelisting Message-ID: <20050822224147.GX10816@nightcrawler> References: <4308E349.8010107@egr.msu.edu> <20050822233323.276ad887@andy.genone.homeip.net> <20050822214059.GU10816@nightcrawler> <20050822235954.4aece5d1@andy.genone.homeip.net> <20050822221915.GV10816@nightcrawler> <430A5353.7030003@egr.msu.edu> 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="ONvqYzh+7ST5RsLk" Content-Disposition: inline In-Reply-To: <430A5353.7030003@egr.msu.edu> User-Agent: Mutt/1.5.8i X-Archives-Salt: 0fa37dbe-1f9e-4c30-96f9-ca085f817a77 X-Archives-Hash: b9318ec1cfee528d8d6ba3ba3b0bc685 --ONvqYzh+7ST5RsLk Content-Type: text/plain; charset=utf8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 22, 2005 at 06:36:03PM -0400, Alec Warner wrote: > I'm kinda with genone on implementing both ( since they are similar ). > If it's decided that blacklisting is easier to maintain, I can always > make up my own whitelist for pkg-foo and apply it and if it works submit > it as a bug ( or even some other whitelist database? ) and thus can > gaurentee that my package was built 'correctly'(TM). I think this would > be important in fex, an enterprise distribution type deal where the > build env is important to some. Put the whitelists in the tree and have > them --excluded by default, so only the users that use them have to > downlaod them. Sticking Yet Another File In Profiles (hence forth known as yafip=20 since it comes up a lot :) is a quick fix, but forces anyone trying to=20 do remote repo's to add hacks to expose that information; effectively=20 requiring two querying modes for the repo, which doesn't seem clean. If it goes anyways, profile would get my vote- base profile exists for=20 spreading settings like this throughout all profiles also; profile and=20 repo are seperated entities, as such the repo implementation doesn't=20 get muddied up, just requires extra keys pulled for profile=20 implementation, which is what it's designed for anyways. ~harring --ONvqYzh+7ST5RsLk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDClSrvdBxRoA3VU0RAumTAKDVuB5THsGFo8Kj87/Os72xOsXWcQCfQnge QeIlpO2Nh/MH7hFxsePcP/4= =8p3n -----END PGP SIGNATURE----- --ONvqYzh+7ST5RsLk-- -- gentoo-portage-dev@gentoo.org mailing list