From: Adam Voigt <adam.voigt@cryptocomm.com>
To: gentoo-dev@gentoo.org
Subject: Re: Re: [gentoo-dev] Prefixed Emerge's
Date: 16 Apr 2002 15:35:09 -0400 [thread overview]
Message-ID: <KERMITKaes8V3qv2agl00000126@kermit.unets.com> (raw)
In-Reply-To: <200204162130.29160.paul@devrieze.net>
If you mean a override switch where an ebuild could turn off allowing
a custom prefix, I would think it would be as simple as at the top of that
ebuild setting PREFIX="", to override the enviorment variable.
Also, if you mean dependenices for each package, I would think those packages
would still go to there default directory (for instance I don't see any reason
for the gnome-lib package to go anywhere but /usr/lib or wherver it needs to go,
plus if they really wanted to, they could just edit the /etc/ld.so.conf if they know
the libraries will be in a special directory).
Adam Voigt
adam.voigt@cryptocomm.com
On Tue, 16 Apr 2002 21:30:29 +0200, Paul de Vrieze <paul@devrieze.net> wrote:
> On Tuesday 16 April 2002 21:06, Adam Voigt wrote:
> > I was just curious if adding the feature of custom prefixes on
> > emerge's (the equivalent of --prefix on a configure) would be
> > terribly hard to do, I ask because I would like to help and don't
> > want to bother those of you working on serious issues with this
> > feature request. As I understand it, all it would really entail is
> > checking if the enviorment variable PREFIX is set and if it is
> > switch PREFIX for /usr or whatever the path is in each ebuild. So
> > for instance, if you were installing mysql if PREFIX = "/usr/mysql"
> > then everything would be set under that directory, so there would
> > be /usr/mysql/var for the actual db, etc. Is this correct? And if
> > it is, does this mean any package which supports custom prefix must
> > have it's ebuild, hand edited? If this is correct I wouldn't mind
> > going through and at least starting on some of more popular
> > packages to add custom pathing's. If I am totally off base on this,
> > I aplogize, this was just what popped into my head as a possible
> > solution to the problem.
> >
>
> Don't forget a lot of software breaks if it is moved to unknown
> directories, so whatever you do, make it an option that an ebuild
> could turn on.
>
> Paul
>
> --
> Paul de Vrieze
> Junior Researcher
> Mail: pauldv@cs.kun.nl
> Homepage: http://www.devrieze.net
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-04-16 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 19:06 [gentoo-dev] Prefixed Emerge's Adam Voigt
2002-04-16 19:30 ` Paul de Vrieze
2002-04-16 19:35 ` Adam Voigt [this message]
2002-04-16 19:38 ` Paul de Vrieze
2002-04-16 19:49 ` Adam Voigt
2002-04-16 19:55 ` Paul de Vrieze
2002-04-16 21:44 ` Arcady Genkin
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=KERMITKaes8V3qv2agl00000126@kermit.unets.com \
--to=adam.voigt@cryptocomm.com \
--cc=gentoo-dev@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