public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE database?
Date: Mon, 3 Dec 2001 10:48:35 -0600	[thread overview]
Message-ID: <20011203104835.E30257@chiba.3jane.net> (raw)
In-Reply-To: <3C0AD02D.8030106@shaw.ca>

On Sun, Dec 02, 2001 at 05:06:53PM -0800, Zach Forrest wrote:
> One thing I think needs some refinement is the USE system. I was 
> thinking that using a format that is more strict would allow for more 
> flexibility and make it easier to automate both the process of 
> generating the make.conf file and for tools to administer the USE 
> variables. It may also allow for some improvements in the Portage system 
> as well.

You're right, our USE system needs refinement, and we are currently
fleshing out details on how to do this.  I agree that we may need a 
master repository of USE variables, and I can code Portage to complain
about "invalid USE variables" if they aren't defined properly.  This
should give everyone the impetus to update a global USE variable 
definition file, making everyone's life easier.  Good idea!

> Using the docs in make.conf as the starting point, I think it would make 
> sense to have a simple database format, or, if using python a list of 
> dictionaries. For example, one entry might look like this:
> 
> use_var={"name":"esd",
>          "description":"Enable enlightenment sound daemon support.",
>          "priority":"OPTIONAL",
>          "depends":"media-sound/esound"}

Sounds like a good plan.  I haven't considered having a "depends" for
every USE variable, but it could come in handy if only for informational
purposes.

> Also, maybe adding a "--satisfyuse" flag to the ebuild/emerge command.

Good idea.

> I know Gentoo is designed for more advanced users and what I have 
> described may seem gratuitous, but I think it might make things easier 
> in the long run. (Also, even advanced users can do with a _little_ 
> convenience.)

Agreed.

> It may, then, also make sense to give a little more structure to the 
> optimization settings. For example:
> 
> optimization_var={
>     "host":"i686",
>     "chost":"i686-pc-linux-gnu",
>     "cflags":"-mcpu=i686 -march=i686 -O3 -pipe",
>     "cxxflags":"-mcpu=i686 -march=i686 -O3 -pipe"}

It would make my life easier if we would use python-based configuration
files.  Right now, they're parsed.  But being able to define dictionaries
is really appealing to me right now :)

> fetch_cmd={
>     "name":"Lukemftp",
>     "command":"/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${y} \${x}"}

Just the idea of using dictionaries for configuration is sounding good
to me right now! :)

> I am thoroughly enjoying Gentoo Linux. Thank you to everyone.

You're welcome.  And thanks for the thought-provoking suggestions :)

-- 
Daniel Robbins                                  <drobbins@gentoo.org>
Chief Architect/President                       http://www.gentoo.org 
Gentoo Technologies, Inc.


  parent reply	other threads:[~2001-12-03 16:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03  1:06 [gentoo-dev] USE database? Zach Forrest
2001-12-03  7:41 ` AW: " Sebastian Werner
2001-12-03  9:13   ` Geert Bevin
2001-12-03 10:02     ` AW: " Sebastian Werner
2001-12-03 10:12       ` Geert Bevin
2001-12-03 11:05         ` AW: " Sebastian Werner
2001-12-03 11:05           ` Geert Bevin
2001-12-03 11:26             ` AW: " Sebastian Werner
2001-12-03 11:32   ` [gentoo-dev] New ideas, USE database, sandbox & more Vitaly Kushneriuk
2001-12-03 11:48     ` Geert Bevin
2001-12-03 12:55       ` Vitaly Kushneriuk
2001-12-03 14:01     ` Joshua Pierre
2001-12-03 16:06       ` Vitaly Kushneriuk
2001-12-03 16:28       ` Daniel Robbins
2001-12-03 18:00         ` Vitaly Kushneriuk
2001-12-03 16:48 ` Daniel Robbins [this message]
2001-12-06  6:01   ` [gentoo-dev] USE database? Mikael Hallendal
2001-12-06 18:12     ` Zach Forrest
2001-12-06 20:38       ` Mikael Hallendal
2001-12-06 22:33         ` Zach Forrest
2001-12-06 23:40           ` Daniel Robbins
2001-12-06 23:52             ` Zach Forrest
2001-12-07 19:28           ` Sebastian Werner
2001-12-07 21:39             ` Daniel Robbins
2001-12-07 21:43               ` Geert Bevin
2001-12-08  1:44               ` Mikael Hallendal

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=20011203104835.E30257@chiba.3jane.net \
    --to=drobbins@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