Hey Moe, he might have run an older version. Dont you remember how many bugfixes you made?
How do you know he's running the latest version..
It works fine with us. He is probably using slackware
I would like to suggest on thing!
Integrate SINP into Vpackager's next version, as a module:http://sinp.sourceforge.net/
or something like that. Imagine vec having its own buildscript repository for packagers. How hard would it be to upgrade packages.
a module to open/browse/search the buildscripts and wget them+the ability of vpackager to handle build scripts and edit them (even if with vnoteedit) = ultimate power
Even buildscripts to work with git,cvs and svn would be awesome to have somewhere on an ftp.
(our own buildscript repository)
One thing that bugs me in slackbuilds repo,is that its buildscripts work with the source of what they have there,older version.If you want to compile wine with a build script from there,first you have to get the latest version of wine from wine website,then edit the build script a bit to change wine version in there,and to change arch to be your (i686), things that vpackager can do. You can make a script that gets the latest avaiable source and compiles it. Vpackager with such a module would be like the gslapt for buildscripts.
sinp doesnt show source version in search
you could only use sinp to search and get the scripts/files, but modify it to support our own server in the future, and vpackager to handle the scripts and innitiate them. Build scripts use the same variables,which can be very good for such an utility.
So i see the future of such an utillity in that way. Having access to slackbuilds repo + access to vec's own repo for such scripts,where build scripts get latest source code,not avaiable version. That would be awesome.