Well, maybe in a autoconf world "Compile Foo 1.0 --help" can call "configure --help" automatically and show all "configure" options and "Compile Foo 1.0 --extra-param --with-my-needed-feature" can pass --with-my-needed-feature to "configure".
It will make the things easy for who just want compile vim with gvim and don't want to change the recipe, but it need a good design to work with other type of recipes as well. In the future, we can can have default --param in the Compile.conf for each package, example: FooDefaultExtraParam = ( "--with-my-needed-feature" "--without-my-not-needed-feature" ) On 12/18/06, Laércio Benedito de Sousa Júnior <[EMAIL PROTECTED]> wrote: > A problem I have with USE flags in Portage is that, sometimes, a lot of > unneeded stuff is installed when I install a given ebuild, just because one > of its dependencies has some unneeded USE flag on. > > Searching in Google, I found some Gentoo users saying they wonder if Portage > could make the installation of packages extensions (activated by USE flags) > similar to the way the things are made in e.g. Debian packages, i.e., if I > install a given "program" with a given USE flag "extensionA" on, and if this > USE flag results in production of additional files, then pack theses files > separately (in Debian convention, we would have a package "program-common", > with the basic stuff, and a package "program-extensionA", with those > additional files). > > In my previous message, when I wrote about the possibility of a single > Recipe to provide several Packages, I'm thinking in this approach. In the > GCC case, the same Recipe could provide the basic Package for GCC, and > separate Packages with additional stuff for GFortran, GCJ, etc. In the Vim > case, we could have a basic Package for Vim and another one with additional > files for GVim. Following this idea, we could also make the Linux kernel > Recipe to provide the version-corresponding Linux-Headers Package, too. > _______________________________________________ > gobolinux-devel mailing list > gobolinux-devel@lists.gobolinux.org > http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel > > > _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
