On Thu, 5 May 2005 03:48:49 -0500 Brian Harring <[EMAIL PROTECTED]> wrote: | > Ok, here's the main issue. Simply changing prefix isn't enough to | > automatically make every package in the tree work. A heck of a lot | > of them will need manual modification, and there's no easy way to | > figure out which these are. So... | | Err. ROOT!="/" exists already, and directly screws with prefixes. So | this doesn't seem particularly valid in light of that fact.
No, root doesn't screw with prefixes. | > Thing is, if we introduce the PREFIX feature, people will expect it | > to actually work. It won't, at least not straight away, because | > there are so many ebuilds that use more than econf to get the prefix | > figured out. By whitelisting we can at least display a nice "you | > can't install this package in a prefix" message. | | Not a valid arguement to exempt even trying. | | Consider if people used that arg for avoiding porting linux to new | arches- Linux would still be strictly x86. Eh? No, see, we have KEYWORDS, which indicate whether you can use a package on a given arch. | > Yet another issue... As it stands, all deps must be installed into | > the given PREFIX. This is messy. Is there a way around this? This | > would be less of a problem with ICANINSTALLTO="home" -- presumably | > for these portage could pass a var to the ebuild telling it in which | > prefix to look for its deps. | | injections, mainly. Nasty hack. -- Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
pgpKZzkoe7eB9.pgp
Description: PGP signature
