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 23:22:59 -0500 [thread overview]
Message-ID: <20051006042259.GR13519@nightcrawler> (raw)
In-Reply-To: <Pine.LNX.4.63.0510061157400.26445@loopy.telegraphics.com.au>
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
On Thu, Oct 06, 2005 at 02:14:32PM +1000, Finn Thain wrote:
>
>
> On Wed, 5 Oct 2005, Kito wrote:
>
> [snip]
> >
> > My first question would be how to identify ebuilds that respect ${prefix}?
> >
> > A separate profile/keyword seems wrong.
> >
> > ICANINSTALLTO was the best idea presented, but that implies it would be
> > a list of known working prefixes, which seems unrealistic.
>
> What problem was ICANINSTALLTO intended to solve? IIRC, it was discussed
> on -dev in the context of vim plug-ins. Apart from vim plugins, has anyone
> found other problem packages?
>
> I'm wondering, would a constraint to the effect that "certain deps of pkg
> foo must be on the same prefix as foo" suffice for the vim plugin case?
>
> Or maybe that would work better if expressed, "pkg blah can not satisfy a
> dep from any pkg on a different prefix". Such constraints would be
> possible to implement with a new file in the profile (say, package.local).
That gets into more of ciaran's HOME installation target feature.
Current form for global prefix offset is
DOMAIN="root offset" , with offset == prefix offset.
If an ebuild doesn't have DOMAIN="offset", and you're doing a prefix
offset, it's unusable. No question of "can I use a dep from another
prefix", with prefix offset you're doing the deps full in an offset.
As stated earlier in this mess of a thread, HOME crap is being left to
those who want it, it'll be implemented by those who want it after
global prefix is ironed out (if it is accepted also).
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-10-06 4:23 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
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 [this message]
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=20051006042259.GR13519@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