public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Cort" <linuxgeek@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Sandboxes
Date: Thu, 23 Mar 2006 19:54:17 -0500	[thread overview]
Message-ID: <3b09e8e90603231654h2e3ec018q22ee4c3ee265324f@mail.gmail.com> (raw)
In-Reply-To: <44233322.2040801@gentoo.org>

> 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). 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.

Cheers!
-Thomas

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-03-24  0:57 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 ` Thomas Cort [this message]
2006-03-24  8:52   ` [gentoo-dev] Sandboxes Paul de Vrieze
2006-03-24  9:42     ` Henrik Brix Andersen
2006-03-24  9:47   ` Kalin KOZHUHAROV
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=3b09e8e90603231654h2e3ec018q22ee4c3ee265324f@mail.gmail.com \
    --to=linuxgeek@gmail.com \
    --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