From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] allowing configuration of builds?
Date: Mon Feb 5 15:31:02 2001 [thread overview]
Message-ID: <3A7F2375.3713598F@gottinger.de> (raw)
In-Reply-To: 20010205144208.D11667@cvs.gentoo.org
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?
Yes I did but that whould make resolving dependencies more difficult.
There might be situations like
package a requires package b (with gnome support).
Such cases are not covered by our current dependencie approach.
So dependencies must look like
a.ebuild
---------
DEPEND="gnome? ( b(gnome) )
!gnome? ( b )"
Which means if a should build with gnome support then we need b with gnome
support.
If a should be build without gnome support we need b (with our without
gnome support).
At the moment we focus on stability and do not want to add more features to
ebuild.
Once packages are all correct, secure and dependencies are all working we
want to
improve configuration.
Daniel is working on a next gen ebuild. I don't think such major
modifications will be made
to our current ebuild but they will make it in the next version.
achim~
>
>
> Pete
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-02-05 22:30 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
2001-02-05 15:31 ` Achim Gottinger [this message]
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=3A7F2375.3713598F@gottinger.de \
--to=320095285153-0001@t-online.de \
--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