On 18/8/08 15:15, "Martin Bähr" <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 18, 2008 at 09:48:52AM -0400, Eric Lake wrote: >> We have all seen people come into the #foresight channel and ask what >> they need to run to get the tools needed to compile apps from source. >> Sure we would rather then just install whatever app it is from the >> repo but they really want to do it themselves. > > what if the stuff is not in the repo? > i don't think most people insist on building stuff from sorcethat is > already available. but rather that the ampunt of stuff available in the > repo is still rather small compared to eg debian. > > when someone asks how to get tools to build from source they should be > guided to start making conary packages and then invited to contribute > them. > > this minimal group could therefore contain all the tools needed to build > and commit a package. or more fine grained, have groups according to the > major recipe classes. (eg all the tools needed to cook an AutoPackageRecipe) > i think these groups could be set up in one recipe by just querying all > the build-dependencies for each recipe class. > > greetings, martin. And when they go to compile it from source and discover that it needs a quick manual patching, this is no problem. But when they go to cook it and discover this, they're going to give up and go manually compile it. Much as it's idealistic that everyone wants to package, I think you'll find most people just want to get the job done, and if compiling and not cooking is the easiest way, that's what they're going to do. Not everyone has the time or motivation to jump in and contribute. I used to, then I just didn't have the time anymore. Cheers, --James _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
