From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=DATE_IN_PAST_12_24,
	INVALID_DATE,MAILING_LIST_MULTI,NO_RELAYS autolearn=no
	autolearn_force=no version=4.0.0
Received: from pete by cvs.gentoo.org with local (Exim 3.22 #1)
	id 14PtmD-0003Tx-00
	for gentoo-dev@gentoo.org; Mon, 05 Feb 2001 15:06:25 -0700
From: Pete Gavin <pete@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] allowing configuration of builds?
Message-ID: <20010205150625.E11667@cvs.gentoo.org>
References: <20010205144208.D11667@cvs.gentoo.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010205144208.D11667@cvs.gentoo.org>; from pete@gentoo.org on Mon, Feb 05, 2001 at 02:42:08PM -0700
Sender: gentoo-dev-admin@gentoo.org
Errors-To: gentoo-dev-admin@gentoo.org
X-BeenThere: gentoo-dev@gentoo.org
X-Mailman-Version: 2.0
Precedence: bulk
Reply-To: gentoo-dev@gentoo.org
List-Help: <mailto:gentoo-dev-request@gentoo.org?subject=help>
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Subscribe: <http://www.gentoo.org/mailman/listinfo/gentoo-dev>,
	<mailto:gentoo-dev-request@gentoo.org?subject=subscribe>
List-Id: Gentoo Linux development list <gentoo-dev.gentoo.org>
List-Unsubscribe: <http://www.gentoo.org/mailman/listinfo/gentoo-dev>,
	<mailto:gentoo-dev-request@gentoo.org?subject=unsubscribe>
List-Archive: <http://www.gentoo.org/pipermail/gentoo-dev/>
Date: Mon Feb  5 15:07:02 2001
X-Original-Date: Mon, 5 Feb 2001 15:06:25 -0700
X-Archives-Salt: 0e6b40e2-a5f6-4ee0-85e1-4b2b5527694c
X-Archives-Hash: 2bcfd5eb0e58ecef17139ac1365f57c6

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