Richard Fish posted <[EMAIL PROTECTED]>, excerpted below, on Sun, 30 Apr 2006 10:28:23 -0700:
> What would be the difference between having a script to create an > ebuild, vs a simple template ebuild to start from? The > /usr/portage/skel.ebuild is all of 17 lines when you ignore comments > and blank lines. And most of that are package settings for > dependancies and source locations and the like. Any script that was > created would have to prompt you for all of that stuff, so running the > script would be just as 'difficult' as copying and modifying the > template. A script that prompted for all that and used the answers to write a simple ebuild wouldn't be so bad. However, it would actually be /more/ work than simply compiling and installing from tarball, so if the object was a quick install of the package, it wouldn't be worth it. OTOH, a simple ebuild generation "wizard" script/applet might be worthwhile in its own right. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-amd64@gentoo.org mailing list