From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Sandboxes
Date: Fri, 24 Mar 2006 18:47:59 +0900 [thread overview]
Message-ID: <4423C04F.4040202@thinrope.net> (raw)
In-Reply-To: <3b09e8e90603231654h2e3ec018q22ee4c3ee265324f@mail.gmail.com>
Thomas Cort wrote:
>> Thoughts on ideas on this somewhat more focussed idea? ( or at least I
>> think it's more focused :P )
>
> Will there be restrictions on what can go into these overlays? There
> are some ebuilds that aren't allowed in the main portage tree. One
> example is winex-cvs (see
> app-emulation/winex-cvs/winex-cvs-3000.ebuild for details).
Interesting comments, and I cannot blame them too much.
> Another
> example... an overlay dev could take an existing ebuild that has
> RESTRICT="fetch" and modify it to fetch the package directly without
> user interaction.
Yes, this one is a good example.
So, in order not to be utterly responsible for distributing such things
as *semi-offcial* gentoo work, I'd suggest just providing a bit easier
way to use external overlays than the current one (which is easy enough
once you set it up, but generally hard for n00bs).
I have my own overlay for quite some time and it had helped a few people,
not counting me (/me != dev) [1]
[1] http://rsync.tar.bz/
I know this is always a topic on whether to have a knife is good or bad,
and whether just possessing a gun makes you a bad guy...
Same is here - if there is a possibility some people will eventually
abuse it. But is this enough to disallow it whatsoever.
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-24 9:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 23:45 [gentoo-dev] Sandboxes Alec Warner
2006-03-24 0:21 ` Stefan Schweizer
2006-03-24 1:15 ` Alec Warner
2006-03-24 0:23 ` Mike Frysinger
2006-03-24 8:51 ` Paul de Vrieze
2006-03-24 15:23 ` Stuart Herbert
2006-03-24 16:32 ` Andrej Kacian
2006-03-24 18:23 ` Mike Frysinger
2006-03-25 2:30 ` [gentoo-dev] Sandboxes Duncan
2006-03-27 20:17 ` Mike Frysinger
2006-03-28 20:31 ` Lars Strojny
2006-03-29 0:32 ` Mike Frysinger
2006-03-24 0:54 ` [gentoo-dev] Sandboxes Thomas Cort
2006-03-24 8:52 ` Paul de Vrieze
2006-03-24 9:42 ` Henrik Brix Andersen
2006-03-24 9:47 ` Kalin KOZHUHAROV [this message]
2006-03-24 15:34 ` Mike Frysinger
2006-03-24 13:37 ` Chris Gianelloni
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=4423C04F.4040202@thinrope.net \
--to=kalin@thinrope.net \
--cc=gentoo-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