From: Brian Harring <ferringb@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Questions about CVS locations and GID...
Date: Wed, 5 Oct 2005 16:34:56 -0500 [thread overview]
Message-ID: <20051005213455.GG10159@nightcrawler> (raw)
In-Reply-To: <AC174E74-3F45-44F0-9D9C-4956C219D116@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On Wed, Oct 05, 2005 at 04:16:06PM -0500, Kito wrote:
> My first question would be how to identify ebuilds that respect $
> {prefix}?
>
> A separate profile/keyword seems wrong.
Agreed.
>
> ICANINSTALLTO was the best idea presented, but that implies it would
> be a list of known working prefixes, which seems unrealistic.
DOMAIN is a saner name imo. Aside from that, listing every potential
target (/usr/bin, $HOME/bin fex) is whacky and getting into the HOME
stuff that comes after.
I would suggest root, and offset as the initial targets.
root would be implicit if DOMAIN isn't defined, and references / as
the prefix. offset is just as it sounds, a root offset, everything
from that tree installed at an offset.
> Maybe
> it would be better to have portage error check that globally at the
> load_config stage against a list of known stupid prefixes,
> stupidprefixes=["/usr","/","/bin"] etc. etc.
Bit beyond the ken of this discussion, but yah, agreed.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-05 21:35 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 18:35 [gentoo-portage-dev] Questions about CVS locations and GID m h
2005-10-05 19:54 ` Ciaran McCreesh
2005-10-05 20:06 ` Alec Joseph Warner
2005-10-05 20:18 ` m h
2005-10-05 20:25 ` Alec Joseph Warner
2005-10-05 20:24 ` Brian Harring
2005-10-05 20:48 ` m h
2005-10-05 21:10 ` Brian Harring
2005-10-05 21:52 ` m h
2005-10-05 22:02 ` Brian Harring
2005-10-05 23:01 ` m h
2005-10-05 23:10 ` Brian Harring
2005-10-05 20:57 ` Ciaran McCreesh
2005-10-05 21:13 ` Brian Harring
2005-10-05 22:31 ` Ciaran McCreesh
2005-10-05 23:00 ` Brian Harring
2005-10-05 23:14 ` Ciaran McCreesh
2005-10-05 23:22 ` Brian Harring
2005-10-05 23:38 ` Ciaran McCreesh
2005-10-05 23:40 ` Brian Harring
2005-10-06 0:13 ` Ciaran McCreesh
2005-10-06 1:01 ` Brian Harring
2005-10-06 1:07 ` Ciaran McCreesh
2005-10-06 1:17 ` Brian Harring
2005-10-06 1:23 ` Ciaran McCreesh
2005-10-06 1:32 ` Brian Harring
2005-10-06 1:40 ` Ciaran McCreesh
2005-10-06 1:48 ` Brian Harring
2005-10-06 2:01 ` Ciaran McCreesh
2005-10-06 2:39 ` Brian Harring
2005-10-06 11:51 ` Ciaran McCreesh
2005-10-06 12:08 ` Jason Stubbs
2005-10-06 13:07 ` Alec Warner
2005-10-06 18:29 ` Ciaran McCreesh
2005-10-06 18:42 ` Brian Harring
2005-10-06 19:11 ` Ciaran McCreesh
2005-10-06 1:56 ` Kito
2005-10-06 2:02 ` Ciaran McCreesh
2005-10-06 2:11 ` Kito
2005-10-05 23:27 ` Alec Warner
2005-10-05 23:38 ` m h
2005-10-05 23:46 ` Alec Warner
2005-10-05 21:16 ` Kito
2005-10-05 21:34 ` Brian Harring [this message]
2005-10-05 22:29 ` Ciaran McCreesh
2005-10-05 22:53 ` Brian Harring
2005-10-05 23:03 ` Ciaran McCreesh
2005-10-05 23:21 ` Brian Harring
2005-10-06 4:14 ` Finn Thain
2005-10-06 4:22 ` Brian Harring
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=20051005213455.GG10159@nightcrawler \
--to=ferringb@gentoo.org \
--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