Re: [gentoo-dev] Ebuild interactivity

[Joshua Brindle]

If this must be done (and it seems like there is pressure to do so) I 
believe the best way is to expand the profile/global/conf language to 
support such choices. For example, if an app needs a mysql host and db 
that can have a 'default' value in the profile (ugh) or the make.global 
file, like MYSQL_HOST, MYSQL_DB. These would be defaults just like all 
other aspects of gentoo (like default CFLAGS, default USE vars, etc) and 
would be overridden by the user in make.conf.

Ebuilds that use such variables could add a warning:

*WARNING: Current MYSQL_HOST is localhost (default)
*WARNING: Change this in make.conf if you need to

then you get rid of the interactivity problem.. the only problem with 
this is a bloated make.global that has variables for probably every 
database type available, etc but it's still a more elegant way than 
asking for input when the ebuild is used.

Joshua Brindle


cbrewer@×××××××××××××.net wrote:

>
>
> This is a rather simplistic approach but..
> Couldn't the interactive ebuilds be flagged in such a way that they would be
> skipped on a world or system emerge, yet still be updated or emerged new via
> an emerge -U <packagename> or emerge <packagename>? I suggest this because it
> would let the bulk of your building get done without hangups, yet still
> provide a way to emerge or update your interactives. Seems easier than trying
> to build AI into portage,imho.


--
gentoo-dev@g.o mailing list