Date: Mon, 12 Nov 2007 16:10:29 -0500 From: Chuck Robey <chuckr@chuckr.org> To: Garrett Cooper <youshi10@u.washington.edu> Cc: "\[LoN\]Kamikaze" <LoN_Kamikaze@gmx.de>, freebsd-questions@freebsd.org, RW <fbsd06@mlists.homeunix.com> Subject: Re: Ports with GUI configs Message-ID: <4738C145.2050601@chuckr.org> In-Reply-To: <4738AEBF.4010109@u.washington.edu> References: <2852884D-270A-4879-B960-C10A602E080E@ashleymoran.me.uk> <47387891.2060007@unsane.co.uk> <47387BCA.6080604@foster.cc> <20071112183502.438b44b8@gumby.homeunix.com.> <4738A71A.6060100@chuckr.org> <4738ACDD.50108@u.washington.edu> <4738ADC8.2060005@gmx.de> <4738AEBF.4010109@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper wrote: > [LoN]Kamikaze wrote: >> Garrett Cooper wrote: >> USE flags are a pain in the ass (former Gentoo user of 3 years). >>> Introducing that type of complexity into a ports system isn't necessary >>> and does unexpected things at times for end-users when developers change >>> variable names or behavior, which happened quite often with Gentoo. >>> make config-all or something similar to have people fill in their >>> desired config info in all of the ncurses config sections would however >>> be a much better idea I think.. >>> -Garrett >>> >> >> Are you talking about make config-recursive? >> > Yes =\. Lemme guess.. that's already an option :)? I hope not. We really need to move this out of being a ports buildtime thing. Currently, to build ports in batch either requires someone to be chained to the computer, so as to intercept all those screens, or to simply agree to install everything, with no inpput whatever. These are both bad options. Also, asking users to pick if a particular piece of software, one that they most liely have never heard of, can be used, is not a particularly good way to get the info either. Gentoo's idea of a USE list has some good points, and some bad points. The worst part is that keeping that USE list corect is too damn difficult. BUT if we made that list private, so be manipulated solely by a more intelligent program, one that could ask better quetions, and let that maintain the list, that would stop the ports-build-time interruptions, and also make things much much easier for users, even technical users, to administer. Just don't let folks need to maintain that list themselves.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4738C145.2050601>