Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[M0E-lnx]

I thought I'd show you guys the status of the new vpackager in the works.

Summary:
In addition to the old vpackager's features, the new release will feature the capabilities to build Cmake applications as well as to packaging python applications.
It auto-guesses the source type, and converts the necessary build options to make a successful build (hopefuly ) on it's own.
A major inprovement (IMO) is the new "Build from cruxports" feature. This is basically a front end to the cruxports4slack that everyone is talking about.
It is written in gambas2, with no bash backend.
The interface remains similiar to the old one for the most part, with a few minor changes, but as far as functionality goes, I believe you guys are gonna like this.

I'll let you all take a peek at the good stuff.

When you fire it up, You'll see this window:


If you chose to build from source, you'll see this


When you make your selection and click next, you'll see this


After the package is built, you can choose to install it, if you do, you'll see this


The slack-desc editor for new slack-desc looks similar to the old one:


Notepad for editing existing description files and .desktop files:


If you choose to Edit an existing package, You'll see this:


And of course, The brand new Build from crux interface:


ATM, I'm in the process of polishing it up a bit, it should be ready for release within the next couple of weeks or so.

Fire up the input!

[exeterdad]

Moe,

I am totally blow away! It's beautiful!
About the Cruxports portion of it.  Will/did our mods mess you up?

[M0E-lnx]

Moe,

I am totally blow away! It's beautiful!
About the Cruxports portion of it.  Will/did our mods mess you up?

More like inspired me
I saw how some of you wanted this thing to build from scripts, but I think this is a much better addition.

Well, uel-sk8s suggested the idea about a week ago on IRC, and I said I'd give it a try.

I think it's a great addition to the project, and an absolutely necessary tool as well.
My front end provides fast and easy search on ports, so the user doesn't have to go through a long list.

In the future, this front end will be able to modify the pkgfiles as well as hopefully add ports repos.
I figure, put this together, plus the old vpackager functions, make it build Cmake sources, package python applications, and you got a pretty handy tool here.

[wcs]

Looks great and brings lots of new features.
Fantastic!

[Toe]

Hm, a cruxports4slack frontend, eh?  Interesting.  Is there any reason you went that route over, say, Emerde (a port of Gentoo's Portage system to Slackware)?

Didn't follow the old thread too closely, sorry if this question has already been answered. 

[rbistolfi]

Wow Moe, that looks great! The interface looks cleaner now, and the new features are awesome. I think this is turning like some kind of ide. Ok you dont write code with vpackager, but you handle different files and process at the same time. May be is a good idea to take that approach for the gui. You could edit Makefiles, build scripts, desc files, etc, in different tabs. A browser panel for easy navigation and access to the files as in the ide programs could be implemented. And you can handle the hole process from a main tab.

Congratulations and we are looking forward to test this new features!

[M0E-lnx]

Hm, a cruxports4slack frontend, eh?  Interesting.  Is there any reason you went that route over, say, Emerde (a port of Gentoo's Portage system to Slackware)?

Didn't follow the old thread too closely, sorry if this question has already been answered. 

This is my first shot at something like this... and we just started using cruxports4slack... so, there it is

[Toe]

Fair enough.  And I suppose down the road you could always add more if desired.  I'd wager Gentoo's repo is much larger than Crux's.

[M0E-lnx]

absolutely. if you take a look at the old thread you can see how this project has evolved from a simple bash script to what it is now. There is a lot of room for expansion and i think this is a useful addition to the project

[blurymind]

wow 

Ok,i absolutely love the new vecpac or should we call it otherwise?
The inclusion of cruxports4slack is a very helpfull feature which will save us the time to google for source tarballs of what we need.
This MUST be included in vector 6 final. Its gonna blow them away.

I've got two questions:
> Do you need any graphic files or polish of old ones?
> is it possible that vlpackager creates slackbuild files of packages it creates, maybe for future releases.

the cruxports penguin icon should look like the official one:


There is a note about cruxports4slack:
"don't install
Crux's port of "core/filesystem", "core/rc" or "core/pkgutils" on Slackware. "
 there should be a note or they should be filthered out (if not already filthered by crux4slack)?

> It would also be great if the user could not only preview the build script, but also edit it (to change version number,etc) and even save it as..  


also At http://crux.nu/portdb/ is a huge collection
of other port repositories. With this you can easily build
Slackware packages for almost every Open Source Software
available.
would be nice if user could use different repositories ( the repo to be configurable in the settings dialogue )
...but i guess that depends on crux4slack development,not vpackager... so anyways, this is one great addition to the packager.
Also,would it be possible (if not already avaiable through cruxports4slack) that it could use a repository that contains build scripts that are not version dependend- that build from svn,git,cvs or something like that. Having the option to add repositories for buildscripts, VL comunity would be able to submit such scripts.

awesome! 
Thank you for developing this amazing piece of software,moe. Vpackager is getting more and more powerful with each release...it exceeded my expectations.

EDIT: Ok,i was so excited that i got to read all the replies from the thread right now. So you are already thinking of the modify buildscript and use different repositories features. This is far better than expected.I never thought you would go for crux. Genius.

maybe http://emerde.freaknet.org/ could be included in future releases. But emerde should be modified just to make packages,not resolve dependencies and install from source directly.... I wonder if its possible to use the same gui frontend on both crux4slack and emerde. Crux is a better choice in my view and probably all the user would need. Still things are getting pretty interesting on the slackware scene. In past years debian got ahead of other distros with its apt-get, now that slackware not only got slapt-get, but it is also adopting get-source-build-package-install systems... It is getting ahead of others by combining in a simple and more free to move way sweet features from the open source world. Making all this avaiable on vector linux and making it configurable and easy to manage just proves vector to be the best slackware based distro out there.

I am also sure that others will be interested in this project or parts of it. Expect to see more folk at the googlecode page.

also,you should change the name:
vlpack or something thats not owned by someone else
Vecpac is occupied by a vector drawing library or something.

[Toe]

In the long term, what do you see as the lifecycle of a package created from this?  Is this strictly just for generating a single .tlz package, or will users be installing them from the same interface?  If I build a package from Cruxports, will it automatically build its dependencies too, and if so, will it also figure out what dependencies I actually need vs ones already on my system?  What about upgrades?

[M0E-lnx]

The life cycle for packages created with this utility is ultimately left out to the user. The application can install the packages upon user request. As far as the crux front end goes this interface will not do anything that the actual back end is unable to do. if you don't have dependancies installed for the application you are compiling the build will fail whether you are building by hand or using this application.

[easuter]

the cruxports penguin icon should look like the official one:

Yeah...but the cruxports penguin looks a bit retarded 

[M0E-lnx]

Have to agree with easuter. That penguin looks mighty ugly. I say for penguin, we keep what I have on there...

@ Blurymind, I will PM you what I need.

[retired1af]

Looks really good! So good in fact, I just may start playing around with building packages when this is released!!!