thats why i proposed vec to have its own buidscript repo,where to put all the build scripts:
*dynamic (latest from cvs)
Going mainstream with this idea will make a slacker weep of happiness
I agree that depending on buildscripts.org is not all that glorious,plus they dont use vec's default configure and checkinstall options (generating tgz instead of tlz)
So what it should do is simple,but how simple is it to achieve in gambas?
search for buildscript(s) -----> show all avaiable versions of buildscripts for package ( to build version x.xx ,x.xb or cvs of source ) --->pick one---> wget and innitiate the script --> compile --> question: save package / install package /edit package (whatever is chosen,package is saved to tmp)
the build script repo can have the written slackdesc,icon,desktop files...
So if sinp can do it,we can do it better.It will take time to collect build scripts for everything,but from the start i think that it is a good idea to have one for each package at the repo. One might need to fetch a newer source of something to build something...this will also save everybody the fuss of searching for a source file over and over again..
Having a search feature to vpackager would not only motivate everybody to submit such scripts,it will also make vector linux more interesting. Maybe other slack-based distros will want to have vpackager with such features, but what is VL's buildscript repo,will remain vl's buildscript repo.