From: Pete Gavin <pete@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] allowing configuration of builds?
Date: Mon Feb 5 15:07:02 2001 [thread overview]
Message-ID: <20010205150625.E11667@cvs.gentoo.org> (raw)
In-Reply-To: <20010205144208.D11667@cvs.gentoo.org>; from pete@gentoo.org on Mon, Feb 05, 2001 at 02:42:08PM -0700
On Mon, Feb 05, 2001 at 02:42:08PM -0700, Pete Gavin wrote:
> Hi,
>
> I was thinking about a way we could allow configuration information to
> be passed to the ebuild scripts at build time. This information could be
> stored in the package database, so that doing "ebuild
> /var/db/pkg/{whatever}/{whatever}.ebuild remerge" would create the exact
> same package as before. We could make it so that if you do something
> like "ebuild {path-to-ebuild-file} query" it will tell you what
> configuration options are available, then you could set those options on
> the ebuild command line. That way, say, for example, there are packages
> that can use gnome, but don't require it, you could do
>
> ebuild {ebuild-file} merge without-gnome
>
> or some such to build it w/o gnome support. The ebuild file will check
> for these options and set the appropriate command line switches to
> configure. You could even cause these options to apply different
> patches. Has anyone else thought about this?
>
Oh, yeah, for example, right now we've got 3 different packages for
emacs; emacs-nogui, emacs-x11, & emacs-motif. With options like this, we
could make it into one package.
Pete
next prev parent reply other threads:[~2001-02-05 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 14:43 [gentoo-dev] allowing configuration of builds? Pete Gavin
2001-02-05 15:07 ` Pete Gavin [this message]
2001-02-05 15:31 ` Achim Gottinger
2001-02-05 15:37 ` Pete Gavin
2001-02-05 15:49 ` Achim Gottinger
2001-02-05 16:02 ` Pete Gavin
2001-02-05 16:33 ` Achim Gottinger
2001-02-05 16:39 ` Pete Gavin
2001-02-05 18:05 ` drobbins
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=20010205150625.E11667@cvs.gentoo.org \
--to=pete@gentoo.org \
--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