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 14PtOi-0003Rb-00
	for gentoo-dev@gentoo.org; Mon, 05 Feb 2001 14:42:08 -0700
From: Pete Gavin <pete@gentoo.org>
To: gentoo-dev@gentoo.org
Message-ID: <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
Subject: [gentoo-dev] allowing configuration of builds?
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 14:43:01 2001
X-Original-Date: Mon, 5 Feb 2001 14:42:08 -0700
X-Archives-Salt: 95e2a304-5d85-441d-a6d2-aac544d78c87
X-Archives-Hash: 2e529e7c11e855936362392b43f3f7a9

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?

Pete