From: Aaron Walker <ka0ttic@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] The merge of emerde with emerge
Date: Fri, 03 Dec 2004 09:06:38 -0500 [thread overview]
Message-ID: <41B072EE.4060408@gentoo.org> (raw)
In-Reply-To: <20041203135311.GA20456@nihil>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alpt wrote:
| On Fri, Dec 03, 2004 at 01:15:33AM -0500, Aaron Walker after a spiritual call
wrote :
| ~>
| ~> | ah, I forgot to say that there's also this:
| ~> | The E_INFODIR, E_LOCALSTATEDIR, E_MANDIR, E_SYSCONFDIR, E_DATADIR
options was
| ~> added
| ~> | in make.conf. With these the user can choose the destination dirs of
thepackages
| ~> | being installed.
| ~>
| ~> The EXTRA_ECONF variable currently exists for this (and anything else the user
| ~> wants to change).
| ~>
| ~> EXTRA_ECONF="--infodir=... --localstatedir=... etc ..."
|
| really?
| then why in econf the ./configure stuff is done with absolute path?
Because those are the defaults. They have to default to something, even if
unspecified (in that case --prefix=/usr/local iirc).
| if you pass to EXTRA_CONF --mandire for example then you'll have
| ./configure --mandir /usr/share/man --mandir USER_SUPPLIED_PATH
| what will happen?
afaik, configure will use the last specified option. If you specify --mandir
twice, it'll use the last specified one (see for yourself). That's probably
the reason EXTRA_ECONF is passed to configure *after* the paths.
| anyway I think it's cleaner to keep E_INFODIR, E_LOCALSTATEDIR,
| E_MANDIR, E_SYSCONFDIR, E_DATADIR separated from EXTRA_CONF
It's your program, so you are more than welcome to. I just wanted to make sure
you were aware that there is already a way to do this.
Cheers
- --
Deliver yesterday, code today, think tomorrow.
Aaron Walker < ka0ttic@gentoo.org > http://dev.gentoo.org/~ka0ttic/
Gentoo/BSD | cron | shell-tools http://butsugenjitemple.org/~ka0ttic/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFBsHLuC3poscuANHARArzXAKCA2b3FWuZWaCT3folGvcsfGm0YMACgh8WY
E9uSDTFYfiJhcjQknbPmXkc=
=j67o
-----END PGP SIGNATURE-----
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-12-03 14:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 17:55 [gentoo-portage-dev] The merge of emerde with emerge Alpt
2004-12-01 19:22 ` Luke-Jr
2004-12-01 20:51 ` Alpt
2004-12-01 22:37 ` Luke-Jr
2004-12-01 23:12 ` Alpt
2004-12-02 0:22 ` Luke-Jr
2004-12-02 16:24 ` Brian Harring
2004-12-03 6:15 ` Aaron Walker
2004-12-03 13:53 ` Alpt
2004-12-03 14:06 ` Aaron Walker [this message]
2004-12-03 14:44 ` [gentoo-portage-dev] " Torsten Veller
2004-12-02 0:26 ` Dennis Bliefernicht
2004-12-02 1:19 ` Colin Kingsley
2004-12-02 1:49 ` Nicholas Jones
2004-12-02 1:52 ` Colin Kingsley
2004-12-02 6:26 ` Alpt
2004-12-03 0:26 ` Dennis Bliefernicht
2004-12-03 3:45 ` Ed Grimm
2004-12-03 4:02 ` Colin Kingsley
2004-12-01 21:14 ` [gentoo-portage-dev] " Colin Kingsley
2004-12-02 12:49 ` Paul de Vrieze
2004-12-02 16:11 ` Brian Harring
2004-12-03 9:01 ` Paul de Vrieze
2004-12-05 13:21 ` Brian Harring
2004-12-06 9:07 ` Marius Mauch
2004-12-01 21:53 ` Ciaran McCreesh
2004-12-02 2:15 ` Nicholas Jones
2004-12-02 13:34 ` Alpt
2004-12-03 4:11 ` Ed Grimm
2004-12-03 7:51 ` Alpt
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=41B072EE.4060408@gentoo.org \
--to=ka0ttic@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