Package builder utility

[M0E-lnx]

vpackager-1.0 is now in the repos...

Please upgrade.

Thanks the the input I got from this thread, I do believe this project has reached a useful and solid enough phase to call it 1.0

Development will of course continue. My goal is to provide an application that can build lots of applications from source, with that said, I'll start working on the next phase of this project, which included support for CMake and python applications, integrating a function to package a build script with every package, and things of that nature.

Please continue testing, and as usual report bugs when you find them.

[blurymind]

i vote two hands to include gslapt in vector's major upgrade release. It will get alot of attention from reviewers, to vector and to itself. I think that we need to polish it up abit. Write a nice documentation and most of all,if possible add a link to our forum ,or to a section in the website for people who would like to become packagers. (i think it would be nice to have a link between the packager utility and the comunity itself).And at the about window,add a link to its official google code page and to a page to report bugs.
EDIT: oh,you already did that. 


Feature request: The ability to create slackbuild files for every package and include it in the package itself.

Bug report: At build process,the create package message doesnt show fully in the window


I really like how you polished it up at places. It looks very very nice.

[caitlyn]

Feature request: The ability to create slackbuild files for every package and include it in the package itself.

YES!  That would be great.

[blurymind]

Feature request: The ability to create slackbuild files for every package and include it in the package itself.

YES!  That would be great.

After that is accomplished, the ability to use slackbuild files for the packages. I think that will be vlpbu's next step.
Think of the possible uses of this. It will make this tool absolutely priceless for packages control. We will also have the slackbuilds included in the packages themselves. Maybe we can upload them at a slackbuild repo dir. That will be very helpful for global organisation.
If its too hard to do,don't do it.

[lagagnon]

i vote two hands to include gslapt in vector's major upgrade release.

I expect you meant "vpackager" and not "gslapt"?

[M0E-lnx]

Is anyone else still getting the same buggy label on the build window?
I thought I submitted a revised package...

a simple slapt-get --install vpackager --reinstall should do the trick

[blurymind]

i vote two hands to include gslapt in vector's major upgrade release.

I expect you meant "vpackager" and not "gslapt"?

yes, i did.
I am sorry guys... these days i am overworked and i tend to be a little bit absent minded. 

Can you believe that this week i have to work saturday and sunday. What are they? Nuts?

[M0E-lnx]

blurymind, can you try a re-install to see if the bug you submitted is still there?

[blurymind]

blurymind, can you try a re-install to see if the bug you submitted is still there?

it is still not at the repo.The one i have,i got from your ftp dir

[M0E-lnx]

There should be one avialable now. I fixed the bug

[Triarius Fidelis]

Development will of course continue. My goal is to provide an application that can build lots of applications from source, with that said, I'll start working on the next phase of this project, which included support for CMake and python applications, integrating a function to package a build script with every package, and things of that nature.

I'll be with you the whole way.

[M0E-lnx]

Great. There is a lot going on at the moment with dynamite development so i got my hands busy now. And besides i need more user input for development to continue. After we get enough bug reports we can get back at it


Looks like someone ran into vpackager from the slacky.it forums
http://www.slacky.eu/forum//viewtopic.php?t=20060&highlight=vpackager

Too bad I dont understand italian.

From what I do gather, and with the aid of google translator, I screwed up in the package creation process.. The permissions of the package's /usr dir are screwed... so I've re-submitted once again, another package.

[blurymind]

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. 

[M0E-lnx]

that would be kool

[blurymind]

that would save  the effort and time to go and download the sources,it will also greatly improve the time for mass compiling.
 

sinp is very cool. I just write

Code:

sinp basket

and it downloads,compiles,packages and installs it.
One downfall is that its source library is kind of poor (slackbuilds for sw12) and outdated (wine was old,among alot of other things and it lacked quite a bit of basic sources)
 Now if we have scrips for compiling the latest source of everything,we wouldn't have to update them(the scripts) ,and we will get serious attention from people interested in buildscripts.It would be great to have them submit scripts.

And the totally kool build script for compiz fusion you gave me, its just a great example of how quick and awesome these scripts are.
I even though of a buildscript icon and the graphic files for that module,but i wont start forging them before i get confirmation they would be used. 
btw i got vpackager work on the pseudo cd,after installing gambas (package for sw12 from slacky)