From: Alec Warner <warnera6@egr.msu.edu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Profiles [ was Environmental Whitelisting ]
Date: Mon, 22 Aug 2005 19:01:27 -0400 [thread overview]
Message-ID: <430A5947.7090604@egr.msu.edu> (raw)
In-Reply-To: <20050822224147.GX10816@nightcrawler>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brian Harring wrote:
> 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
> since it comes up a lot :) is a quick fix, but forces anyone trying to
> do remote repo's to add hacks to expose that information; effectively
> 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
> spreading settings like this throughout all profiles also; profile and
> repo are seperated entities, as such the repo implementation doesn't
> get muddied up, just requires extra keys pulled for profile
> implementation, which is what it's designed for anyways.
> ~harring
Hijacking the thread for a moment, has anyone looked into the profiles
redesign/rewrite/ syndication from web -> storage, flatfiles -> DMBS,
etc...It will need to be abstracted just the same as everything
else...Or they should be ;)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQwpZRmzglR5RwbyYAQJkPg//aisGvUvmh6f6XRXxIyydhaX/ec6ZpCg6
h+o7pcENYZDLO8W/SbLDOCvHsULAO0aPhK8cKGxiD2bDb/jD2Qi/2g7QxcCWjcxT
wzE1WyTGeTTlGLeR2GnGt+ZFvrZczuTKvy29fkPnXYZRWl31rFDlm2TaRD4ArNAt
3QGIJIBSAw1xRrg1T66ovKn8Ilwzw+nyvWVwV8jEB6fxo5gOtSr1pUOLqWO8FnVR
Pz0uPoVCn+OSQQRttmPaHhihDGIRnWsT58RcNZP8n/4cFqgGGpQ9wkXY/9QRhCFs
SKFpSYQY42xOH1th1hXrAQvUfXqEjALVBXLRm/aWadnGcpzySEL/p14zSMz2hXux
tBkIoosFSaOyudFD6hwAIznBAzqt61hAOvFGpFcQdUenyuh+bRR1wnKkgz6rSG9v
VB4rs+ZW12Q2QGjOkfhx06XvsoQUpEwAaEH1/kvV/7t/Kz1YhFP/01I9eVT0Zzvn
klV/AhrCHml319yu1WPuWjMGL9E5LLMC7FNgBzfiWSxk7WBsACSdm+EXcyFzDPvs
A6vS6mLouPMgbch5VT/8sw+KWfEGqTRwxfu0Gw+mzj3atNYmByoNPgVg2mQYatJs
+atlR/hRuTTnv0WV7dqtNLFuLCqBfoJTXPOuc5qsTSJaYGyAnZREk+kttF7TyTG8
qMdx+2/zvBc=
=c82h
-----END PGP SIGNATURE-----
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-22 23:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 20:25 [gentoo-portage-dev] Environment Whitelisting Alec Warner
2005-08-22 1:24 ` Zac Medico
2005-08-22 3:52 ` [gentoo-portage-dev] " Drake Wyrm
2005-08-22 4:41 ` Zac Medico
2005-08-22 16:29 ` Kristian Benoit
2005-08-22 14:52 ` Jason Stubbs
2005-08-22 18:08 ` Zac Medico
2005-08-22 19:15 ` warnera6
2005-08-22 19:24 ` Zac Medico
2005-08-22 20:58 ` Brian Harring
2005-08-23 1:57 ` Kristian Benoit
2005-08-23 2:15 ` Brian Harring
2005-08-22 21:33 ` [gentoo-portage-dev] " Marius Mauch
2005-08-22 21:40 ` Brian Harring
2005-08-22 21:55 ` warnera6
2005-08-22 21:59 ` Marius Mauch
2005-08-22 22:19 ` Brian Harring
2005-08-22 22:36 ` Alec Warner
2005-08-22 22:41 ` Brian Harring
2005-08-22 23:01 ` Alec Warner [this message]
2005-08-22 23:28 ` Jason Stubbs
2005-08-22 23:56 ` Brian Harring
2005-08-23 10:50 ` Jason Stubbs
2005-08-23 0:27 ` Alec Warner
2005-08-23 2:46 ` Kristian Benoit
2005-08-23 3:40 ` Alec Warner
2005-08-23 16:19 ` Kristian Benoit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=430A5947.7090604@egr.msu.edu \
--to=warnera6@egr.msu.edu \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox