VectorLinux

Cooking up the Treats => General Development => Topic started by: M0E-lnx on September 14, 2007, 09:07:42 am

Title: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 14, 2007, 09:07:42 am
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:
(http://img153.imageshack.us/img153/9763/mainbf8.th.jpg) (http://img153.imageshack.us/my.php?image=mainbf8.jpg)

If you chose to build from source, you'll see this
(http://img212.imageshack.us/img212/8024/buildsrcza7.th.jpg) (http://img212.imageshack.us/my.php?image=buildsrcza7.jpg)

When you make your selection and click next, you'll see this
(http://img527.imageshack.us/img527/6408/fbuildingdi1.th.jpg) (http://img527.imageshack.us/my.php?image=fbuildingdi1.jpg)

After the package is built, you can choose to install it, if you do, you'll see this
(http://img529.imageshack.us/img529/3452/installgh5.th.jpg) (http://img529.imageshack.us/my.php?image=installgh5.jpg)

The slack-desc editor for new slack-desc looks similar to the old one:
(http://img263.imageshack.us/img263/7070/newdescqz6.th.jpg) (http://img263.imageshack.us/my.php?image=newdescqz6.jpg)

Notepad for editing existing description files and .desktop files:
(http://img212.imageshack.us/img212/1891/fnotepadzu3.th.jpg) (http://img212.imageshack.us/my.php?image=fnotepadzu3.jpg)

If you choose to Edit an existing package, You'll see this:
(http://img509.imageshack.us/img509/4569/feditpackagefy4.th.jpg) (http://img509.imageshack.us/my.php?image=feditpackagefy4.jpg)

And of course, The brand new Build from crux interface:
(http://img522.imageshack.us/img522/7227/fcruxty6.th.jpg) (http://img522.imageshack.us/my.php?image=fcruxty6.jpg)

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!
Title: Re: The New vpackager Thread - take a peak
Post by: exeterdad on September 14, 2007, 09:59:02 am
Moe,

I am totally blow away! It's beautiful!
About the Cruxports portion of it.  Will/did our mods mess you up?
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 14, 2007, 10:04:07 am
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.
Title: Re: The New vpackager Thread - take a peak
Post by: wcs on September 14, 2007, 11:24:57 am
Looks great and brings lots of new features.
Fantastic!
Title: Re: The New vpackager Thread - take a peak
Post by: Toe on September 14, 2007, 02:23:55 pm
Hm, a cruxports4slack frontend, eh?  Interesting.  Is there any reason you went that route over, say, Emerde (http://emerde.freaknet.org/) (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.  :-X
Title: Re: The New vpackager Thread - take a peak
Post by: rbistolfi on September 14, 2007, 03:03:21 pm
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!
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 14, 2007, 03:19:24 pm
Hm, a cruxports4slack frontend, eh?  Interesting.  Is there any reason you went that route over, say, Emerde (http://emerde.freaknet.org/) (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.  :-X

This is my first shot at something like this... and we just started using cruxports4slack... so, there it is
Title: Re: The New vpackager Thread - take a peak
Post by: Toe on September 14, 2007, 04:07:17 pm
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.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 14, 2007, 04:23:18 pm
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
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on September 14, 2007, 11:57:51 pm
wow  :o

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:
(http://yhafri.club.fr/crux/penguin.gif)

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!  ;D
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.
Title: Re: The New vpackager Thread - take a peak
Post by: Toe on September 15, 2007, 01:02:18 pm
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?
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 15, 2007, 01:31:41 pm
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.
Title: Re: The New vpackager Thread - take a peak
Post by: easuter on September 15, 2007, 01:40:40 pm
Quote from: blurymind
the cruxports penguin icon should look like the official one:
(http://yhafri.club.fr/crux/penguin.gif)

Yeah...but the cruxports penguin looks a bit retarded  :D
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 15, 2007, 02:22:07 pm
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.
Title: Re: The New vpackager Thread - take a peak
Post by: retired1af on September 15, 2007, 04:38:17 pm
Looks really good! So good in fact, I just may start playing around with building packages when this is released!!!  ;D
Title: Re: The New vpackager Thread - take a peak
Post by: InTheWoods on September 15, 2007, 07:02:21 pm
This is definitely an impressive addition to Vector!
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 18, 2007, 11:11:14 am
Ok... Silly idea just popped into my head....

Since the new vpackager will have a GUI for cruxports....
Is anyone else interested in creating our very own ports repository?
We could use this to build or very own distro-specific stuff (maybe the stuff that you're advised not to build from slack)?
Could also include ports to build stuff like what blurymind was suggesting ... dynamic scripts... only instead of a script repo it would be ports. Using the backend and front end we already have.
Of course, we can also offer ports to build newer versions of other applications as well...

I'd like to get everyone's opinion and reaction to this... and see how many would be willing to help...
This would need maintenance as well.
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on September 24, 2007, 10:59:18 am
well, i suggested the repo,because then vec community will have more control over its own repo- we will be able to fix non-working scripts...add scripts..have a way for vlpackager to collect information from its own community's database (like a way to warn the user of ports that are known not to work)

 I like the idea of scripts that build from git,cvs,svn.. because the code there is alive and you get the latest, edgy stuff. Moe sent me such a script a while ago that builds compiz and i thought that it is pretty nifty,because latest compiz usually has most bugfixes and additional new plugins.Specially for some applications it is sometimes best to get the latest source..I called this kind of ports "dynamic",because the source there is changing and they dont need to be updated and are avaiable (pretty nifty).
Some weeks ago i got latest gimp from svn through a process that can be easily automated via a script and i found it to be very stable,not to mention all the sweet new features it has..
Another example for niftiness of scripts that build from cvs/svn is wine. Wine is under rapid development and every week a new version comes out with lots of patches applied to it.I personally like to have latest wine and submit information to winehq about what works and what not (if everything changes/breaks).
I think that it is still early to see how things develop,but i really do think that what is done here is very exciting.

few other applications worth an eye are
(alternative to zbrush?- well it has the basics)
http://sharp3d.sourceforge.net/mediawiki/index.php/Main_Page
http://www.dedalo-3d.com/index.php
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 24, 2007, 11:02:11 am
blurymind... I think you can accomplish this via the portage thingie...

It may need a little time to figure it out, but I think it might work.
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on September 24, 2007, 11:31:16 am
i cant seem to get it to work under my vl59...

I think i have the wrong version of gambas and its runtime. The gambas package i got from linuxpackages sw12 repo... the runtime one was by default installed...

I wonder what to do now. I get this err
Code: [Select]
root:# vpackager
/usr/bin/env: gbr2: No such file or directory

is it possible to edit the scripts before innitiating them?
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 24, 2007, 12:20:14 pm
You need this
http://vectorlinux.osuosl.org/veclinux-5.9/unstable/base/gambas2-runtime-1.9.51-i586-1vl59.tlz

EDIT:
easuter is working on putting together a package that contains the essentials for vpackager to run without this type of glitches...
We should have a revised package in the repos soon.
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on September 24, 2007, 01:29:42 pm
Code: [Select]
gbr2: error while loading shared libraries: libgnuintl.so.8: cannot open shared object file: No such file or directory
i tried after installing gettext from sw12 official repo and running ldconfig, i get the same error.
 :(
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 24, 2007, 02:07:52 pm
You need intltool
Title: Re: The New vpackager Thread - take a peak
Post by: Joe1962 on September 24, 2007, 05:18:16 pm
Code: [Select]
ln -sf /usr/lib/preloadable_libintl.so /usr/lib/libintl.so
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on September 25, 2007, 10:33:09 am
Code: [Select]
ln -sf /usr/lib/preloadable_libintl.so /usr/lib/libintl.so
thank you,joe.This fied it. :)
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 25, 2007, 12:57:50 pm
I've been adding stuff to the wiki and updating the screen shots. vvucic will also be helping me with the wiki... so go ahead.. check that out too
Title: Re: The New vpackager Thread - take a peak
Post by: InTheWoods on September 26, 2007, 12:26:29 pm
This is perfect! I read through the other thread you had on this and I definitely see this becoming the standard method for installing software from source. I know it's still a work in progress but this is what I would have wanted as a beginner (meaning I still want it).
Quote
I've been adding stuff to the wiki and updating the screen shots. vvucic will also be helping me with the wiki... so go ahead.. check that out too
I think you should spin off your section of the " How to install software from source code" into a separate article. Just link to your how to from mine from its present position in the document. That way someone who does not want to install from the command line but winds up in my how to can find yours. Perhaps I should rename mine to "How to install source code from the command line". Do you want those images from the top of this thread in your wiki article?

If you want I will make those changes for you. Unless of course you and vvucic have other plans.
"VPACKAGER the VL 6.0 source code installer" sound okay for a title?

This could be a major turning point for how software gets installed. Keep up the good work!
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 26, 2007, 01:25:23 pm
You can make those changes... I really suck at wiki and doc writing... so if you can think of any way to make the wiki better, please do it.
I think you need a gmail account to make changes.

PM me your gmail address, and I'll add you to the project
Title: Re: The New vpackager Thread - take a peak
Post by: InTheWoods on September 27, 2007, 05:08:45 am
Here is your wiki article
http://vectorlinux.com/wiki/doku.php?id=howtos:vpackager
Quote
I think you need a gmail account to make changes.
I am not sure what I need a GMAIL account for. If it's for the wiki articles I do not. Although I would not mind being more involved in it, I am somewhat unreliable for things that require timely attention.
If you just want to mail me new features and pictures to be included in the wiki, sure. But the above shortcoming still applies. vvucic is probably a better bet. But I will help if I can.

1 I did not use all of your pictures because I was not sure where to put them. If you want to add them
2 just put your cursor on the edit page where you want them.
3 click the picture frame on the bar above the editing area
4 upload your picture when the upload window appears
5 double click on the uploaded picture that appears in the same window

and your done. Your picture will appear in the wiki right where your cursor is.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 27, 2007, 05:44:52 am
Ahh... that wiki.... I thought you were referring to this http://code.google.com/p/vpackager/wiki/HowToUse

Well, in that case, you can take over the vpackager part of the VL wiki any time you feel like it... ;)
vvucic will keep the vpackager wiiki (link above) updated.
Title: Re: The New vpackager Thread - take a peak
Post by: saulgoode on September 27, 2007, 09:59:52 am
One of the things I really appreciate about Slackware (and thusly Vector) is that, with very few exceptions, the packages are built from source code which is unmodified from that available from the originating project's homepages. This minimizes risk of errors creeping into a package and eases the task of customizing a project to my own needs. Better still, it allows me to readily contribute back to a project or otherwise participate in its development.

Randomly scanning through some of the "packages" (actually just scripts) in the Crux repositories, I see that many of them follow this same practice (of obtaining source directly from the project). However, I do not see a ready way to determine if or when this is the case (I had to manually compare the sources specified in the scripts with the projects' source locations); and determining what modifications might have been made to the source if it is from a different location.

So, my first concern is about how this "chain of custody" of package source is to be addressed.

In addition, Crux packaging guidelines seem to specify three practices that are at odds with guidelines of Slackware (and, to my knowledge, Vector):
It appears that the only benefits of incorporating Crux ports packaging into Vector would be the catalog of available Crux scripts and the fact that a packager doesn't have to search for a project's homepage for source. It seems to me, the first benefit would be better covered by implementation of a repository of Vector-Build scripts (something which would probably be necessary anyway, owing to the differing guidelines between Crux and Vector); and the second benefit is pretty well nullified by the fact that packagers will need to document any disparities between the included sources and those of the originating project (knowledge necessary to the Vectelopers, if not the users).

The NLS problem is easily handled automatically, but for the other concerns, using Crux ports might entail more effort than it saves.




Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 27, 2007, 11:09:01 am
As far as I know, the cruxports thing here is more like a universal build script that can be controlled by using a function on a file named "Pkgfile".

Here is a sample from the few port scripts I've written to jump start this whole thing... they're located here http://vectorlinux.osuosl.org/veclinux-5.9/ports/

Code: [Select]
# Description: GTK+ based IRC client
# URL: http://www.xchat.org/
# Maintainer: M0E-lnx
# Optimized to include support for gettext, and to disable the old
textfe, also added patch
# Depends on: openssl, gtk, perl

name=xchat
version=2.8.4
release=2
source=(http://www.xchat.org/files/source/2.8/$name-$version.tar.bz2
        http://www.xchat.org/files/source/2.8/patches/xc284-scrollbmkdir.diff)

build() {
        cd $name-$version
        patch -p1 -i $SRC/xc284-scrollbmkdir.diff --verbose
        ./configure --prefix=/usr \
                --enable-openssl \
                --enable-perl \
                --enable-ipv6 \
                --disable-gnome \
                --enable-gtkfe \
                --disable-textfe \
                --disable-python \
                --disable-tcl \
                --with-included-gettext \
                --disable-nls
        make
        make DESTDIR=$PKG install
        rm -rf $PKG/usr/{etc,share}
        install -D $name.desktop $PKG/usr/share/applications/$name.desktop
        install -D $name.png $PKG/usr/share/pixmaps/$name.png
}


The enable / disable language support and / or other features are controlled by the build procedure for each application IIRC.
To add to that, IIRC, the cruxports4slack package that we are hosting has been modified to make up-to-vector-standards packages. As you can see from the sample script, it works pretty much like a slackbuild. The build procedure can be fully customized to fit each application. Even the binary stripping can be done and the documentation packaging.

Title: Re: The New vpackager Thread - take a peak
Post by: InTheWoods on September 27, 2007, 08:14:34 pm
Quote
Ahh... that wiki....
This is the third VL related Wiki I've learned of in as many weeks.

Clearly I skimmed over the previous thread on this to quickly. I take it the Google Wiki is for this project only.
I added links in the DokuWiki to the Google Wiki How To's and downloads. That should  take care of things for now.

I also declared you (M0E-lnx) as the author of the vecpackager article in the DokuWiki. 99% of it was relocated material from your vpackager section in How to install software from source code.

Hope you don't mind.

Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 27, 2007, 09:10:47 pm
Not at all. I guess we'll just have to check it every once in a while to make it's up to date. The wiki at the project page will change in the near future as we get it polished up a bit
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on September 30, 2007, 08:38:43 am

Code: [Select]
=======> ERROR: Md5sum mismatch found:
MISSING   feecc3ccb4639b672d8446154a4fb700  wine-0.9.45.tar.bz2
NEW       aa729097ddb324185a3e092b37a5f9fe  wine-0.9.46.tar.bz2
=======> ERROR: Building '/usr/ports/opt/wine/wine-0.9.46-i586-1vl59.tlz' failed.
Result: FAILED
can we disable mdsums check? Whenever I edit the build file to match latest version of something, i get to this errer,right after its source is downloaded.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 30, 2007, 08:58:17 am
can we disable mdsums check? Whenever I edit the build file to match latest version of something, i get to this errer,right after its source is downloaded.

Right-click on the port name, select "Check md5sum" it will fix this for you if there is a md5sum mismatch ;)

You can also bypass the md5sum check when you click on "Build selected" a new window comes up showing the package name, and offers you to select which tag to use for the package... There is a "Install after build" checkbox and then there is a "ignore md5sum" checkbox... just check the box, and it will bypass the md5sum test
Title: Re: The New vpackager Thread - take a peak
Post by: saulgoode on September 30, 2007, 12:24:11 pm
@MOE-lnx

Thanks for the response. I was starting to get the impression that CRUX repositories would be relied upon for Vector packages. For the reasons stated, I think that would eventually cause grief for the Vector developers.

I think a better solution would be for your build script -- rather than doing the compilation -- to locate the appropriate source & SlackBuild (and DL if needed), apply any patches needed (either updates or VL-specific changes), define the appropriate environment variables, and then call the SlackBuild script (as mentioned previously, this is close to the approach taken by DarkVision's SlackPacks (http://www.mkanet.de/index.html)).

By using the existing SlackBuild baseline, compatibility with the Slackware base would be encouraged and, in the long run, entail less maintenance effort on the part of Vector's developers.



Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on September 30, 2007, 02:18:26 pm
I can understand your concern, however, if anyone plans to submit packages built from cruxports, they should modify the Pkgfile to reflect a good slackware-compattible build. This could be done with the GUI from the "Actions" > "Advanced" > "Modify build file" menu

The crux bacend is completely capable of patching if necessary and adjusting anything that may need to be.

At the end of the day, everyone chooses their way of packaing, some prefer typing the commands hemselves, while other like the slackbuild method, and others, like the idea of automating the process as much as possible, and just changing what needs to be changed in the script.

This is what crux does. It is a base script whose build procedure can be shaped in any form one needs to.

I have started working on some VectorLinux scripts myself. Anyone who wants to contribute can look at the samples, and use them as a template to get going. I figure, with this, eventually we can have our very own ports repository that can be very useful, and easy to contribute too. ;)
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on October 01, 2007, 05:56:35 am
awesome. This is exactly the best approach i can think of too.
I would love to submit such scripts for our ports-repo...
I think that having a little tut at the wiki for that would be absolutely neat.
A simple and well put script can be easily edited to fit different applications.

=)  ... not to mention that at our ports repo,we will have our own slack-desc files,which include more info such as application website,author... if possible build date and packager id... being applied to it (or its getting too complicated..). Having more control over the process will make us all feel more comfortable with the ports,and using them.
I am still enthusiastic about the build from svn/cvs/git scripts....
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on October 01, 2007, 10:07:49 am
If you want to contribute to the ports repo, make a directory called "ports" in your vectorcontrib account, and let me know, I'll add them to the repos
Title: Re: The New vpackager Thread - take a peak
Post by: Dweeberkitty on October 14, 2007, 03:52:54 pm
Hey MOE-lnx,
Is it possible that your program (looking very sweet BTW) could write SlackBuilds or some similar script? I guess this would be called a feature request.  ;)

I'd like to have Vpackager write the scripts automatically, or on demand, so one doesn't have to write the scripts manually. Keep up the good work!
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on October 14, 2007, 07:03:56 pm
That is absolutely possible... I'll start working on it As soon as I get a chance

_EDIT_
BTW, I just released RC2.
The GUI looks a lot better, and the cruxports4slack has a lot more features...

Please upgrade now ;)
Title: Re: The New vpackager Thread - take a peak
Post by: Dweeberkitty on October 14, 2007, 09:25:41 pm
_EDIT_
BTW, I just released RC2.
The GUI looks a lot better, and the cruxports4slack has a lot more features...

Please upgrade now ;)

I had just downloaded it when I posted. :) It looks great!
Title: Re: The New vpackager Thread - take a peak
Post by: Dweeberkitty on October 24, 2007, 08:46:47 pm
Hey MOE-lnx!

You've already got Python and Cmake support. How much more would it take for you to implement Scons support? That would help with a lot of applications that unfortunately use the scons system instead of a standard Make or Cmake.

Your app is great! Keep it up. I love it.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on October 25, 2007, 08:06:41 am
scons can be done and it's in the plans for the near future. However the current cmake support still needs lots of testing. I'd like to get you all to test that and get all the bugs in that area worked out before adding support for scons. I tested the python support myself and it seemed ok but i also need others to test. Specially now because i don't have as much time to spare for this project so i'll be relying a lot more on bug reports to get it done
Title: Re: The New vpackager Thread - take a peak
Post by: Freeman on December 25, 2007, 04:38:19 am
Hi there
I tried to make a package using Vpackager provided with VL-5.9, to make Katapult.
http://katapult.kde.org/ On a vanilla build it always fails..

Code: [Select]
vpackager Building katapult-0.3.2.1-i586-1vl59.tlz
----------------------------------------------------
BASIC PACKAGE CONFIGURATION
--prefix=/usr
--sysconfdir=/etc
--bindir=/usr/bin
--libdir=/usr/lib
--mandir=/usr/man
--localstatedir=/var
----------------------------------------------------
ADDITIONAL CONFIGURATION
 --with-included-gettext

COMPILER FLAGS: -O2 -march=i586 -mtune=i686

Begin extracting sources
katapult-0.3.2.1/
katapult-0.3.2.1/ChangeLog
katapult-0.3.2.1/admin/
katapult-0.3.2.1/admin/cvs.sh
tar: katapult-0.3.2.1/ChangeLog: Cannot utime: No such file or directory
tar: katapult-0.3.2.1/ChangeLog: Cannot change ownership to uid 1000, gid 1000: No such file or directory
tar: katapult-0.3.2.1/ChangeLog: Cannot change mode to rw-r--r--: No such file or directory
tar: katapult-0.3.2.1/admin: Cannot mkdir: No such file or directory
katapult-0.3.2.1/admin/doxygen.sh
tar: katapult-0.3.2.1/admin/cvs.sh: Cannot open: No such file or directory
katapult-0.3.2.1/admin/bcheck.pl
katapult-0.3.2.1/admin/missing
tar: katapult-0.3.2.1/admin/doxygen.sh: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/bcheck.pl: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/missing: Cannot open: No such file or directory
katapult-0.3.2.1/admin/Doxyfile.am
katapult-0.3.2.1/admin/depcomp
katapult-0.3.2.1/admin/am_edit
tar: katapult-0.3.2.1/admin/Doxyfile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/depcomp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/am_edit: Cannot open: No such file or directory
katapult-0.3.2.1/admin/debianrules
katapult-0.3.2.1/admin/configure.in.min
katapult-0.3.2.1/admin/conf.change.pl
katapult-0.3.2.1/admin/ltmain.sh
tar: katapult-0.3.2.1/admin/debianrules: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/configure.in.min: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/conf.change.pl: Cannot open: No such file or directory
katapult-0.3.2.1/admin/config.pl
katapult-0.3.2.1/admin/deps.am
tar: katapult-0.3.2.1/admin/ltmain.sh: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/config.pl: Cannot open: No such file or directory
katapult-0.3.2.1/admin/libtool.m4.in
tar: katapult-0.3.2.1/admin/deps.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/libtool.m4.in: Cannot open: No such file or directory
katapult-0.3.2.1/admin/Doxyfile.global
katapult-0.3.2.1/admin/install-sh
katapult-0.3.2.1/admin/configure.in.bot.end
katapult-0.3.2.1/admin/ylwrap
katapult-0.3.2.1/admin/config.guess
tar: katapult-0.3.2.1/admin/Doxyfile.global: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/install-sh: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/configure.in.bot.end: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/ylwrap: Cannot open: No such file or directory
katapult-0.3.2.1/admin/detect-autoconf.pl
katapult-0.3.2.1/admin/mkinstalldirs
katapult-0.3.2.1/admin/nmcheck
katapult-0.3.2.1/admin/pkg.m4.in
katapult-0.3.2.1/admin/config.sub
tar: katapult-0.3.2.1/admin/config.guess: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/detect-autoconf.pl: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/mkinstalldirs: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/nmcheck: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/pkg.m4.in: Cannot open: No such file or directory
katapult-0.3.2.1/admin/Makefile.common
katapult-0.3.2.1/admin/oldinclude.m4.in
katapult-0.3.2.1/admin/acinclude.m4.in
tar: katapult-0.3.2.1/admin/config.sub: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/Makefile.common: Cannot open: No such file or directory
tar: katapult-0.3.2.1/admin/oldinclude.m4.in: Cannot open: No such file or directory
katapult-0.3.2.1/admin/compile
tar: katapult-0.3.2.1/admin/acinclude.m4.in: Cannot open: No such file or directory
katapult-0.3.2.1/COPYING
tar: katapult-0.3.2.1/admin/compile: Cannot open: No such file or directory
katapult-0.3.2.1/doc/
katapult-0.3.2.1/doc/katapult/
katapult-0.3.2.1/doc/katapult/katapult2.png
katapult-0.3.2.1/doc/katapult/index.docbook
tar: katapult-0.3.2.1/COPYING: Cannot open: No such file or directory
tar: katapult-0.3.2.1/doc: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/doc/katapult: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/doc/katapult/katapult2.png: Cannot open: No such file or directory
katapult-0.3.2.1/doc/katapult/katapult1.png
tar: katapult-0.3.2.1/doc/katapult/index.docbook: Cannot open: No such file or directory
katapult-0.3.2.1/doc/katapult/katapult0.png
katapult-0.3.2.1/doc/katapult/Makefile.am
tar: katapult-0.3.2.1/doc/katapult/katapult1.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/doc/katapult/katapult0.png: Cannot open: No such file or directory
katapult-0.3.2.1/doc/katapult/Makefile.in
katapult-0.3.2.1/doc/Makefile.am
katapult-0.3.2.1/doc/Makefile.in
tar: katapult-0.3.2.1/doc/katapult/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/doc/katapult/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/doc/Makefile.am: Cannot open: No such file or directory
katapult-0.3.2.1/aclocal.m4
tar: katapult-0.3.2.1/doc/Makefile.in: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/
katapult-0.3.2.1/katapult/katapult.kdevses
katapult-0.3.2.1/katapult/katapult.kdevelop
tar: katapult-0.3.2.1/aclocal.m4: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult.kdevses: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/katapult/
katapult-0.3.2.1/katapult/katapult/hi128-app-katapult.png
katapult-0.3.2.1/katapult/katapult/katapultsettings.cpp
katapult-0.3.2.1/katapult/katapult/hi32-app-katapult.png
katapult-0.3.2.1/katapult/katapult/katapultconfigtar: katapult-0.3.2.1/katapult/katapult.kdevelop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/hi128-app-katapult.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/katapultsettings.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/hi32-app-katapult.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/katapultconfigdlg.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/katapultiface.h: Cannot open: No such file or directory
dlg.h
katapult-0.3.2.1/katapult/katapult/katapultiface.h
katapult-0.3.2.1/katapult/katapult/hi64-app-katapult.png
katapult-0.3.2.1/katapult/katapult/main.cpp
tar: katapult-0.3.2.1/katapult/katapult/hi64-app-katapult.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/main.cpp: Cannot openkatapult-0.3.2.1/katapult/katapult/katapultsettings.h
katapult-0.3.2.1/katapult/katapult/hi16-app-katapult.png
katapult-0.3.2.1/katapult/katapult/katapult.h
katapult-0.3.2.1/katapult/katapult/settings.cpp
katapult-0.3.2.1/katapult/katapult/Makefile.am
kata: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/katapultsettings.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/hi16-app-katapult.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/katapult.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/settings.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/confcatalogs.ui: Cannot open: No such file or directory
pult-0.3.2.1/katapult/katapult/confcatalogs.ui
katapult-0.3.2.1/katapult/katapult/hisc-app-katapult.svgz
katapult-0.3.2.1/katapult/katapult/confdisplay.ui
katapult-0.3.2.1/katapult/katapult/katapultconfigdlg.cpp
tar: katapult-0.3.2.1/katapult/katapult/hisc-app-katapult.svgz: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/confdisplay.ui: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/katapult/katapult.cpp
katapult-0.3.2.1/katapult/katapult/Makefile.in
tar: katapult-0.3.2.1/katapult/katapult/katapultconfigdlg.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/katapult.cpp: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/katapult/katapult.desktop
katapult-0.3.2.1/katapult/katapult/confgeneral.ui
tar: katapult-0.3.2.1/katapult/katapult/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/katapult.desktop: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/katapult/hi22-app-katapult.png
katapult-0.3.2.1/katapult/katapult/hi48-app-katapult.png
katapult-0.3.2.1/katapult/configure.in.in
tar: katapult-0.3.2.1/katapult/katapult/confgeneral.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/hi22-app-katapult.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/katapult/hi48-app-katapult.png: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/common/
katapult-0.3.2.1/katapult/common/katapultdisplay.cpp
katapult-0.3.2.1/katapult/common/imagedisplay.h
katapult-0.3.2.1/katapult/common/katapultitem.h
katapult-0.3.2.1/katapult/common/status.h
katapult-0.3.2.1/katapult/commotar: katapult-0.3.2.1/katapult/configure.in.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultdisplay.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/imagedisplay.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultitem.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/status.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultaction.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/actionregistry.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultdisplay.h: Cannot open: No such file or directory
n/katapultaction.cpp
katapult-0.3.2.1/katapult/common/actionregistry.cpp
katapult-0.3.2.1/katapult/common/katapultdisplay.h
katapult-0.3.2.1/katapult/common/imagedisplaysettings.ui
katapult-0.3.2.1/katapult/common/katapultcatalog.cpp
katapult-0.3.2.1/katapult/common/actionregistry.h
katapult-0.3.2.1/katapult/common/cachedcatalog.cpp
katapult-0.3.2.1/katapult/common/Makefile.am
tar: katapult-0.3.2.1/katapult/common/imagedisplaysettings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultcatalog.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/actionregistry.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/cachedcatalog.cpp: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/common/match.cpp
katapult-0.3.2.1/katapult/common/katapultaction.h
katapult-0.3.2.1/katapult/common/imagedisplay.cpp
katapult-0.3.2.1/katapult/common/cachedcatalog.h
tar: katapult-0.3.2.1/katapult/common/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/match.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultaction.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/imagedisplay.cpp: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/common/katapultcatalog.desktop
katapult-0.3.2.1/katapult/common/Makefile.in
tar: katapult-0.3.2.1/katapult/common/cachedcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultcatalog.desktop: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/common/katapultitem.cpp
katapult-0.3.2.1/katapult/common/match.h
katapult-0.3.2.1/katapult/common/katapultcatalog.h
katapult-0.3.2.1/katapult/common/katapultdisplay.desktop
tar: katapult-0.3.2.1/katapult/common/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultitem.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/match.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/common/katapultdisplay.desktop: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/NEWS
katapult-0.3.2.1/katapult/configure.files
katapult-0.3.2.1/katapult/Makefile.am
katapult-0.3.2.1/katapult/plugins/
katapult-0.3.2.1/katapult/plugins/catalogs/
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/
katapult-tar: katapult-0.3.2.1/katapult/NEWS: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/configure.files: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/katapult_spellcatalog.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/actioncopyspelling.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/crsc-action-katapultspellcheck.svgz: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/spelling.cpp: Cannot open: No such file or directory
0.3.2.1/katapult/plugins/catalogs/spellcatalog/katapult_spellcatalog.desktop
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/actioncopyspelling.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/crsc-action-katapultspellcheck.svgz
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/spelling.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/spellcatalog.h
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/cr128-action-katapultspellcheck.png
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/spelling.h
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/settings.ui
katapult-0.3.2.1/katapult/plutar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/spellcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/cr128-action-katapultspellcheck.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/spelling.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/settings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/actioncopyspelling.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/spellcatalog.cpp: Cannot open: No such file or directory
gins/catalogs/spellcatalog/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/actioncopyspelling.h
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/spellcatalog.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/Makefile.in
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/googlecatalog.cpp
tar: katapult-0.3.2.1/katapult/plugins/catalogs/spellcatalog/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog: Cannot mkdir: No such file or directory
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/query.h
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/katapult_googlecatalog.desktop
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/googlecatalog.h
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/googlecatalog.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/query.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/katapult_googlecatalog.desktop: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/actionsearch.h
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/query.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/settings.ui
katapult-0.3.2.1/katapult/plugins/catalogs/googltar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/googlecatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/actionsearch.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/query.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/settings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/Makefile.am: Cannot open: No such file or directory
ecatalog/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/Makefile.in
katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/actionsearch.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/actionevalexpr.cpp
katapult-0.3.2.1/katapult/plugins/catalotar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/googlecatalog/actionsearch.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/actionevalexpr.cpp: Cannot open: No such file or directory
gs/calculatorcatalog/hi128-action-checkmark.png
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/hi128-action-no.png
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/actionevalexpr.h
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/parser.cpp
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/hi128-action-checkmark.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/hi128-action-no.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/actionevalexpr.h: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/expression.h
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/hi128-app-xcalc.png
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/parser.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/expression.h: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/parser.y
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/calculatorcatalog.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/katapult_calculatorcatalog.desktop
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/hi128-app-xcalc.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/parser.y: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/calculatorcatalog.cpp: Cannot open: No such file or directory
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/settings.ui
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/katapult_calculatorcatalog.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/settings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/calculatorcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/expression.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/actionrun.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/execcatalog.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/command.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/command.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/settings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/actionrun.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/katapult_execcatalog.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/execcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/bookmarkcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/actionopenbookmark.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/bookmark.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/actionopenbookmark.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/bookmarkcatalog.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/katapult_bookmarkcatalog.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/mozillabookmark.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/settings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/mozillabookmark.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/bookmark.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/directory.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/actionopendocument.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/documentcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/documentcatalog.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/document.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/directory.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/document.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/settings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/katapult_documentcatalog.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/actionopendocument.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/actionrunprogram.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/program.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/katapult_programcatalog.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/programcatalog.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/program.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/actionrunprogram.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/settings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/programcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/coverimage.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/song.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/song.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/settings.ui: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/amarokcatalog.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/amarokcatalog.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/actionplaysong.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/actionplaysong.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/coverimage.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/katapult_amarokcatalog.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/catalogs/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay/puredisplay.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay/puredisplay.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay/qembed_images.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay/katapult_puredisplay.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay/doublebg.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay/singlebg.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/puredisplay/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display/katapult_o2display.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display/o2display.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display/qembed_images.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display/doublebg.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display/singlebg.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/o2display/o2display.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay/katapult_glassdisplay.desktop: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay/qembed_images.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay/glassdisplay.cpp: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay/glassdisplay.h: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay/doublebg.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay/singlebg.png: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/display/glassdisplay/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/plugins/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/Doxyfile: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/katapult/COPYING-DOCS: Cannot open: No such file or directory
tar: katapult-0.3.2.1/configure.in.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/Makefile.am.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/README: Cannot open: No such file or directory
tar: katapult-0.3.2.1/subdirs: Cannot open: No such file or directory
tar: katapult-0.3.2.1/configure: Cannot open: No such file or directory
tar: katapult-0.3.2.1/configure.files: Cannot open: No such file or directory
tar: katapult-0.3.2.1/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/INSTALL: Cannot open: No such file or directory
tar: katapult-0.3.2.1/TODO: Cannot open: No such file or directory
tar: katapult-0.3.2.1/config.h.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/configure.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/AUTHORS: Cannot open: No such file or directory
tar: katapult-0.3.2.1/acinclude.m4: Cannot open: No such file or directory
tar: katapult-0.3.2.1/Makefile.cvs: Cannot open: No such file or directory
tar: katapult-0.3.2.1/configure.in.bot: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/sv: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/sv/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/sv/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/sv/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/sv/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/it: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/it/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/it/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/it/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/it/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pt_BR: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/pt_BR/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pt_BR/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pt_BR/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pt_BR/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/sk: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/sk/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/sk/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/sk/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/sk/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/es: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/es/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/es/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/es/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/es/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/el: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/el/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/el/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/el/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/el/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/nl: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/nl/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/nl/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/nl/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/nl/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ru: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/ru/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ru/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ru/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ru/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/et: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/et/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/et/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/et/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/et/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/tr: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/tr/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/tr/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/tr/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/tr/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ga: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/ga/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ga/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ga/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ga/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/nb: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/nb/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/nb/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/nb/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/nb/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/uk: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/uk/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/uk/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/uk/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/uk/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pl: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/pl/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pl/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pl/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pl/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ja: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/ja/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ja/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ja/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ja/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/fr: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/fr/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/fr/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/fr/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/fr/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/br: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/br/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/br/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/br/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/br/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/da: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/da/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/da/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/da/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/da/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pt: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/pt/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pt/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pt/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/pt/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ar: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/ar/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ar/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ar/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ar/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/bg: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/bg/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/bg/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/bg/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/bg/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/cs: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/cs/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/cs/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/cs/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/cs/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ca: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/ca/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ca/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ca/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/ca/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/hu: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/hu/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/hu/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/hu/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/hu/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/de: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/de/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/de/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/de/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/de/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/gl: Cannot mkdir: No such file or directory
tar: katapult-0.3.2.1/po/gl/katapult.po: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/gl/katapult.gmo: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/gl/Makefile.am: Cannot open: No such file or directory
tar: katapult-0.3.2.1/po/gl/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1/Makefile.in: Cannot open: No such file or directory
tar: katapult-0.3.2.1: Cannot utime: No such file or directory
tar: katapult-0.3.2.1: Cannot change ownership to uid 1000, gid 1000: No such file or directory
tar: katapult-0.3.2.1: Cannot change mode to rwxr-xr-x: No such file or directory
tar: Error exit delayed from previous errors
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/calculatorcatalog.h
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/Makefile.in
katapult-0.3.2.1/katapult/plugins/catalogs/calculatorcatalog/expression.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/actionrun.h
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/execcatalog.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/command.h
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/command.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/settings.ui
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/actionrun.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/katapult_execcatalog.desktop
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/execcatalog.h
katapult-0.3.2.1/katapult/plugins/catalogs/execcatalog/Makefile.in
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/bookmarkcatalog.h
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/actionopenbookmark.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/bookmark.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/actionopenbookmark.h
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/bookmarkcatalog.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/katapult_bookmarkcatalog.desktop
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/mozillabookmark.h
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/settings.ui
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/Makefile.in
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/mozillabookmark.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/bookmarkcatalog/bookmark.h
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/directory.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/actionopendocument.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/documentcatalog.h
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/documentcatalog.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/document.h
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/directory.h
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/document.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/settings.ui
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/katapult_documentcatalog.desktop
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/actionopendocument.h
katapult-0.3.2.1/katapult/plugins/catalogs/documentcatalog/Makefile.in
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/actionrunprogram.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/program.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/katapult_programcatalog.desktop
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/programcatalog.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/program.h
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/actionrunprogram.h
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/settings.ui
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/programcatalog.h
katapult-0.3.2.1/katapult/plugins/catalogs/programcatalog/Makefile.in
katapult-0.3.2.1/katapult/plugins/catalogs/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/coverimage.h
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/song.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/song.h
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/settings.ui
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/amarokcatalog.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/amarokcatalog.h
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/Makefile.am
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/actionplaysong.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/actionplaysong.h
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/coverimage.cpp
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/katapult_amarokcatalog.desktop
katapult-0.3.2.1/katapult/plugins/catalogs/amarokcatalog/Makefile.in
katapult-0.3.2.1/katapult/plugins/catalogs/Makefile.in
katapult-0.3.2.1/katapult/plugins/display/
katapult-0.3.2.1/katapult/plugins/display/puredisplay/
katapult-0.3.2.1/katapult/plugins/display/puredisplay/puredisplay.h
katapult-0.3.2.1/katapult/plugins/display/puredisplay/puredisplay.cpp
katapult-0.3.2.1/katapult/plugins/display/puredisplay/qembed_images.h
katapult-0.3.2.1/katapult/plugins/display/puredisplay/katapult_puredisplay.desktop
katapult-0.3.2.1/katapult/plugins/display/puredisplay/Makefile.am
katapult-0.3.2.1/katapult/plugins/display/puredisplay/doublebg.png
katapult-0.3.2.1/katapult/plugins/display/puredisplay/singlebg.png
katapult-0.3.2.1/katapult/plugins/display/puredisplay/Makefile.in
katapult-0.3.2.1/katapult/plugins/display/Makefile.am
katapult-0.3.2.1/katapult/plugins/display/o2display/
katapult-0.3.2.1/katapult/plugins/display/o2display/katapult_o2display.desktop
katapult-0.3.2.1/katapult/plugins/display/o2display/o2display.cpp
katapult-0.3.2.1/katapult/plugins/display/o2display/qembed_images.h
katapult-0.3.2.1/katapult/plugins/display/o2display/Makefile.am
katapult-0.3.2.1/katapult/plugins/display/o2display/doublebg.png
katapult-0.3.2.1/katapult/plugins/display/o2display/singlebg.png
katapult-0.3.2.1/katapult/plugins/display/o2display/Makefile.in
katapult-0.3.2.1/katapult/plugins/display/o2display/o2display.h
katapult-0.3.2.1/katapult/plugins/display/Makefile.in
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/katapult_glassdisplay.desktop
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/qembed_images.h
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/glassdisplay.cpp
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/glassdisplay.h
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/Makefile.am
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/doublebg.png
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/singlebg.png
katapult-0.3.2.1/katapult/plugins/display/glassdisplay/Makefile.in
katapult-0.3.2.1/katapult/plugins/Makefile.am
katapult-0.3.2.1/katapult/plugins/Makefile.in
katapult-0.3.2.1/katapult/Doxyfile
katapult-0.3.2.1/katapult/Makefile.in
katapult-0.3.2.1/katapult/COPYING-DOCS
katapult-0.3.2.1/configure.in.in
katapult-0.3.2.1/Makefile.am.in
katapult-0.3.2.1/README
katapult-0.3.2.1/subdirs
katapult-0.3.2.1/configure
katapult-0.3.2.1/configure.files
katapult-0.3.2.1/Makefile.am
katapult-0.3.2.1/INSTALL
katapult-0.3.2.1/TODO
katapult-0.3.2.1/config.h.in
katapult-0.3.2.1/configure.in
katapult-0.3.2.1/AUTHORS
katapult-0.3.2.1/acinclude.m4
katapult-0.3.2.1/Makefile.cvs
katapult-0.3.2.1/configure.in.bot
katapult-0.3.2.1/po/
katapult-0.3.2.1/po/sv/
katapult-0.3.2.1/po/sv/katapult.po
katapult-0.3.2.1/po/sv/katapult.gmo
katapult-0.3.2.1/po/sv/Makefile.am
katapult-0.3.2.1/po/sv/Makefile.in
katapult-0.3.2.1/po/it/
katapult-0.3.2.1/po/it/katapult.po
katapult-0.3.2.1/po/it/katapult.gmo
katapult-0.3.2.1/po/it/Makefile.am
katapult-0.3.2.1/po/it/Makefile.in
katapult-0.3.2.1/po/pt_BR/
katapult-0.3.2.1/po/pt_BR/katapult.po
katapult-0.3.2.1/po/pt_BR/katapult.gmo
katapult-0.3.2.1/po/pt_BR/Makefile.am
katapult-0.3.2.1/po/pt_BR/Makefile.in
katapult-0.3.2.1/po/sk/
katapult-0.3.2.1/po/sk/katapult.po
katapult-0.3.2.1/po/sk/katapult.gmo
katapult-0.3.2.1/po/sk/Makefile.am
katapult-0.3.2.1/po/sk/Makefile.in
katapult-0.3.2.1/po/es/
katapult-0.3.2.1/po/es/katapult.po
katapult-0.3.2.1/po/es/katapult.gmo
katapult-0.3.2.1/po/es/Makefile.am
katapult-0.3.2.1/po/es/Makefile.in
katapult-0.3.2.1/po/el/
katapult-0.3.2.1/po/el/katapult.po
katapult-0.3.2.1/po/el/katapult.gmo
katapult-0.3.2.1/po/el/Makefile.am
katapult-0.3.2.1/po/el/Makefile.in
katapult-0.3.2.1/po/nl/
katapult-0.3.2.1/po/nl/katapult.po
katapult-0.3.2.1/po/nl/katapult.gmo
katapult-0.3.2.1/po/nl/Makefile.am
katapult-0.3.2.1/po/nl/Makefile.in
katapult-0.3.2.1/po/ru/
katapult-0.3.2.1/po/ru/katapult.po
katapult-0.3.2.1/po/ru/katapult.gmo
katapult-0.3.2.1/po/ru/Makefile.am
katapult-0.3.2.1/po/ru/Makefile.in
katapult-0.3.2.1/po/et/
katapult-0.3.2.1/po/et/katapult.po
katapult-0.3.2.1/po/et/katapult.gmo
katapult-0.3.2.1/po/et/Makefile.am
katapult-0.3.2.1/po/et/Makefile.in
katapult-0.3.2.1/po/tr/
katapult-0.3.2.1/po/tr/katapult.po
katapult-0.3.2.1/po/tr/katapult.gmo
katapult-0.3.2.1/po/tr/Makefile.am
katapult-0.3.2.1/po/tr/Makefile.in
katapult-0.3.2.1/po/ga/
katapult-0.3.2.1/po/ga/katapult.po
katapult-0.3.2.1/po/ga/katapult.gmo
katapult-0.3.2.1/po/ga/Makefile.am
katapult-0.3.2.1/po/ga/Makefile.in
katapult-0.3.2.1/po/nb/
katapult-0.3.2.1/po/nb/katapult.po
katapult-0.3.2.1/po/nb/katapult.gmo
katapult-0.3.2.1/po/nb/Makefile.am
katapult-0.3.2.1/po/nb/Makefile.in
katapult-0.3.2.1/po/uk/
katapult-0.3.2.1/po/uk/katapult.po
katapult-0.3.2.1/po/uk/katapult.gmo
katapult-0.3.2.1/po/uk/Makefile.am
katapult-0.3.2.1/po/uk/Makefile.in
katapult-0.3.2.1/po/pl/
katapult-0.3.2.1/po/pl/katapult.po
katapult-0.3.2.1/po/pl/katapult.gmo
katapult-0.3.2.1/po/pl/Makefile.am
katapult-0.3.2.1/po/pl/Makefile.in
katapult-0.3.2.1/po/ja/
katapult-0.3.2.1/po/ja/katapult.po
katapult-0.3.2.1/po/ja/katapult.gmo
katapult-0.3.2.1/po/ja/Makefile.am
katapult-0.3.2.1/po/ja/Makefile.in
katapult-0.3.2.1/po/fr/
katapult-0.3.2.1/po/fr/katapult.po
katapult-0.3.2.1/po/fr/katapult.gmo
katapult-0.3.2.1/po/fr/Makefile.am
katapult-0.3.2.1/po/fr/Makefile.in
katapult-0.3.2.1/po/Makefile.am
katapult-0.3.2.1/po/br/
katapult-0.3.2.1/po/br/katapult.po
katapult-0.3.2.1/po/br/katapult.gmo
katapult-0.3.2.1/po/br/Makefile.am
katapult-0.3.2.1/po/br/Makefile.in
katapult-0.3.2.1/po/da/
katapult-0.3.2.1/po/da/katapult.po
katapult-0.3.2.1/po/da/katapult.gmo
katapult-0.3.2.1/po/da/Makefile.am
katapult-0.3.2.1/po/da/Makefile.in
katapult-0.3.2.1/po/pt/
katapult-0.3.2.1/po/pt/katapult.po
katapult-0.3.2.1/po/pt/katapult.gmo
katapult-0.3.2.1/po/pt/Makefile.am
katapult-0.3.2.1/po/pt/Makefile.in
katapult-0.3.2.1/po/ar/
katapult-0.3.2.1/po/ar/katapult.po
katapult-0.3.2.1/po/ar/katapult.gmo
katapult-0.3.2.1/po/ar/Makefile.am
katapult-0.3.2.1/po/ar/Makefile.in
katapult-0.3.2.1/po/bg/
katapult-0.3.2.1/po/bg/katapult.po
katapult-0.3.2.1/po/bg/katapult.gmo
katapult-0.3.2.1/po/bg/Makefile.am
katapult-0.3.2.1/po/bg/Makefile.in
katapult-0.3.2.1/po/cs/
katapult-0.3.2.1/po/cs/katapult.po
katapult-0.3.2.1/po/cs/katapult.gmo
katapult-0.3.2.1/po/cs/Makefile.am
katapult-0.3.2.1/po/cs/Makefile.in
katapult-0.3.2.1/po/ca/
katapult-0.3.2.1/po/ca/katapult.po
katapult-0.3.2.1/po/ca/katapult.gmo
katapult-0.3.2.1/po/ca/Makefile.am
katapult-0.3.2.1/po/ca/Makefile.in
katapult-0.3.2.1/po/hu/
katapult-0.3.2.1/po/hu/katapult.po
katapult-0.3.2.1/po/hu/katapult.gmo
katapult-0.3.2.1/po/hu/Makefile.am
katapult-0.3.2.1/po/hu/Makefile.in
katapult-0.3.2.1/po/Makefile.in
katapult-0.3.2.1/po/de/
katapult-0.3.2.1/po/de/katapult.po
katapult-0.3.2.1/po/de/katapult.gmo
katapult-0.3.2.1/po/de/Makefile.am
katapult-0.3.2.1/po/de/Makefile.in
katapult-0.3.2.1/po/gl/
katapult-0.3.2.1/po/gl/katapult.po
katapult-0.3.2.1/po/gl/katapult.gmo
katapult-0.3.2.1/po/gl/Makefile.am
katapult-0.3.2.1/po/gl/Makefile.in
katapult-0.3.2.1/Makefile.in
Result: FAILED

I know it needs KDE libs, but they are included in VL-5.9 if I recall correctly.

I'm now trying it the manual way: configure --without-arts, make & checkinstall -L
Title: Re: The New vpackager Thread - take a peak
Post by: Freeman on December 25, 2007, 05:07:56 am
Package made without a  hitch... It's up and running now :)
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on December 25, 2007, 06:07:40 am
i can confirm this tar bug myself. First time you try to create the package it fails due to tar error.This happens always, so you must go back and then click start again,so it begins the building (second time it finds the directory).

I myself cant compile streamtuner due to a make error.  :(

I made a port file:

Quote
# streamtuner
# Description: Streamtuner is a stream directory browser.
# Maintainer: blurymind
# Depends on  Gtk+,libcurl,libxml2(opt),taglib(opt),Python(opt),PyGtk(opt)
name=streamtuner
version=0.99.99
release=1

source=(http://savannah.nongnu.org/download/$name/$name-$version.tar.gz)

build() {
cd $name-$version
./configure --prefix=/usr \
 --sysconfdir=/etc \
 --mandir=/usr/man
 --with-included-gettext


make
make DESTDIR=$PKG install
}       
wouldnt it be awesome if we had a ports thread,where people post their custom port scripts and others test them.That way this feature will be made more accessable and easy to learn. Right now i cant even find a link to the wiki. This current website is just terrible.Navigation is hard even for those who have visited it (including myself) and there are no links to the wiki and no integration with the living parts of the community.This is a scruffy package for such an awesome distro and community.

Feature request for vpackager: option to open port script from user directory and execute it.Also "save as" option to its custom text editor. ::)
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on December 25, 2007, 06:54:42 am
There i a bug in the current version with the untar process. I have fixed it but don't have the means to upload the newer release at the moment
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on December 25, 2007, 07:45:11 am
ok,building package from tarball,doesnt seem to write the slack-desk (package has no description) . Thats when i go back and the front again.

it says it has created a /tmp/vpackager-builds/slack-desc file, but when i navigate to that directory,there is no file there.Not even anything to "overwrite"

edit: i found the mistake- it creates a file,but its name is not the same as what it looks for later:
vpackager-buildsslack-desc. A missing "/" somewhere in the code is the root of the problem.

also related to the tar error:
Quote
Begin extracting sources
sh: line 0: cd: /tmp/vpackager-builds: No such file or directory
Result: FAILED
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on December 25, 2007, 01:25:28 pm
more bugs and feature requests i'm afraid...

feature requests
cruxports4slack:  file>open pkgfile (browse for a script from local directory,and add it to list Imported/$name)

bugs
cruxports4slack: after building package and installing it,package is nowhere to be found. Not even at /tmp/
would be nice to store packages at some folder at tmp that doesnt get wiped out each time vpackager is closed.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on December 25, 2007, 02:01:45 pm
the crux front end's build process is a little different. The resulting package will not show up in /tmp. this is done to maintain compatibility with the back end. packages built using the vpackager gui for crux are kept in /usr/ports/repo/app
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on December 25, 2007, 02:17:39 pm
thats a bit unconvenient. Will a repo refreshh clean these direcotries of all the leftovers?
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on December 25, 2007, 03:03:36 pm
you can select the application's name and right-click to perform a clean up and other tasks
Title: Re: The New vpackager Thread - take a peak
Post by: kidd on December 25, 2007, 03:48:16 pm
Can we have a local 'repository' instead of /usr/ports/VL ?

When I'm testing, I'd like to be able to have a 'scratch' repo. and it seems I can't add repos. I can only enable/disable the listed ones.

Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on December 26, 2007, 06:07:46 am
Can we have a local 'repository' instead of /usr/ports/VL ?

When I'm testing, I'd like to be able to have a 'scratch' repo. and it seems I can't add repos. I can only enable/disable the listed ones.


You can really test wherever you like. I have my "test" ports in ~/area-51/ports.
After a port has been tested and proven to work, you can upload it to your vectorcontrib account to share it.

You can execute pkgmk from anywhere you have a Pkgfile.

Keep in mind that vpackager will only list the repos under /usr/ports/ and not any of your "testing" repos. If you want vpackager to list it, you'll have to move it or copy it to /usr/ports/<repo_name>/<app>

Adding repos to cruxports is a little different as well. IIRC, the normal procedure goes like this:
* Write a <repo_name>.httpup file in /etc/ports
* Create the repo's root dir
* Create the entries for the repo (your ports)
if you can do that, then vpackager will pick them up and let you enable / disable them.

BTW, a Disabled repo means that vpackager will not update that repo when you hit the "update" button, the local contents are still there, but may get outdated if the repo remains "disabled" for a long time
Title: Re: The New vpackager Thread - take a peak
Post by: kidd on December 26, 2007, 09:33:41 am
vectorcontrib account? If I'm going to write ports for about 10 apps, do I need an account, or I should send them to official packagers?

What's the procedure to get a vectorcontrib account? I've found nothing about that in VL site/forum

Thanks!
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on December 26, 2007, 10:13:37 am
vectorcontrib account? If I'm going to write ports for about 10 apps, do I need an account, or I should send them to official packagers?

What's the procedure to get a vectorcontrib account? I've found nothing about that in VL site/forum

Thanks!

Contact Johnb316 to get setup with a vectorcontrib account. You can upload your packages and ports there and then a repo maintenance guy will move them to the appropriate section of the forums.

To get your vectorcontrib account you must PM Johnb316.
Title: Re: The New vpackager Thread - take a peak
Post by: kidd on December 28, 2007, 09:10:59 am
I've installed zsh with the usual process (download tar.gz , ./configure, make install ) , after that, when I browse through vpackager (cruxports4slack).  I'll try to reproduce it and find out exact conditions that lead to this, but for the moment,  that's all the info..
 
http://img301.imageshack.us/img301/8389/screenxz9.jpg
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on December 28, 2007, 09:14:48 am
@ kidd
could you post your /usr/ports/opt/zsh/Pkgfile ?

BTW, which version of vpackager is that?
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on January 02, 2008, 09:56:51 am
the biggest bug is that vpackager doesnt actually put the slack-desc file in the packages  :-\
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on January 02, 2008, 10:01:42 am
BTW, I have fixed this problem, and was able to upload it to svn.
The latest code (if compiled and packaged) should have this problem corrected.

I plan to release a package as soon as I can get my DSL service back. Unless someone else volunteers to compile it and make the package.
Title: Re: The New vpackager Thread - take a peak
Post by: easuter on January 04, 2008, 07:52:47 am
BTW, I have fixed this problem, and was able to upload it to svn.
The latest code (if compiled and packaged) should have this problem corrected.

I plan to release a package as soon as I can get my DSL service back. Unless someone else volunteers to compile it and make the package.

And it will be a lot easier to package now that Gambas2 is finally a 2.0.0!!! Woohoo!  ;D
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on January 04, 2008, 09:03:26 am
And it will be a lot easier to package now that Gambas2 is finally a 2.0.0!!! Woohoo!  ;D
Yes it will.. BTW easuter, should we now just package the binary instead of all the libs with it?
Title: Re: The New vpackager Thread - take a peak
Post by: easuter on January 04, 2008, 09:17:44 am
Yeah, I think so, now that Gambas2 can be added to the extra repo safely, it should be like making any other ordinary package.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on January 04, 2008, 09:43:36 am
kook. the phone co is supposed to fix my DSL today, if that happens, I should have a new vpackager and vasmCC uploaded by monday
Title: Re: The New vpackager Thread - take a peak
Post by: MikeCindi on March 10, 2008, 07:39:25 am
Sorry, in a bit of a hurry so I haven't researched the board for a solution yet but...
I continually get the following:
Code: [Select]
vpackager Building openvpn-2.0.9-i586-1vl59.tlz
----------------------------------------------------
BASIC PACKAGE CONFIGURATION
--prefix=/usr
--sysconfdir=/etc
--bindir=/usr/bin
--libdir=/usr/lib
--mandir=/usr/man
--localstatedir=/var
----------------------------------------------------
ADDITIONAL CONFIGURATION
 --with-included-gettext

COMPILER FLAGS: -O2 -march=i586 -mtune=i686

Begin extracting sources
sh: line 0: cd: /tmp/vpackager-builds: No such file or directory
Result: FAILED
This happens with every release of vpackager, on every tarball I try to build, using the default settings on my machine. I have tried removing/changing the build options, etc. also without success. I then revert to building manually as the popup says to do. That is no problem but surely the default settings on a clean VL install (whether 5.8/9 std or 5.8/9 SOHO) should get past this point. I will put a bit more effort into it later this week...
BTW, the above was attempted on 5.9 SOHO alpha 3.3.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on March 10, 2008, 08:24:38 am
Mikecindy. I'm sorry to inform that there is a serious bug in the code that keeps deleting the temp dir.
I was sort of hoping to come up with some improvements and fix this bug, but it seems to be taking me much longer than the estimated time...

I will start working on a bugfix release to fix this issue
Title: Re: The New vpackager Thread - take a peak
Post by: MikeCindi on March 10, 2008, 04:45:20 pm
Whew, I was beginning to think this was just me.  ;)
I am a patient person though and eagerly awaiting more testing material.
Thanks for your efforts thus far as this will be/is a valuable package for the VL community.
Title: Re: The New vpackager Thread - take a peak
Post by: blurymind on March 13, 2008, 07:56:01 am
latest vpackager1.0.10b , cant edit build scripts from cruxports.

actions>edit build scipt gives an error: this application has encountered an unexpected error and must abort. "[45] file or directory doesnt exist. MbuildFromCrux.?.0 "
the appplication closes.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on March 13, 2008, 07:59:18 am
You're right... Dunno how that happened.

I think this one will wait until the next release comes along. (giving you guys something to look forward to ;) )

I will make a bug entry just so I dont forget to look at it... Thanks for pointing it out
How is the build from source working for you?
Title: Re: The New vpackager Thread - take a peak
Post by: hata_ph on April 13, 2008, 08:23:33 pm
Dunno anyonw having the same problem but last night i upgrade vpackager to version 1.0.10b-i586-1vl59.tlz and now i cannot run vpackager. It show below error.....

Quote
root:# vpackager
gbr2: error while loading shared libraries: libffi.so.5: cannot open shared object file: No such file or directory
Title: Re: The New vpackager Thread - take a peak
Post by: uelsk8s on April 13, 2008, 08:38:12 pm
libffi is in the testing repo. enable it and run slapt-get --update && slapt-get --install libffi
Title: Re: The New vpackager Thread - take a peak
Post by: hata_ph on April 13, 2008, 08:44:49 pm
libffi is in the testing repo. enable it and run slapt-get --update && slapt-get --install libffi

I have enable the testing repo and gslapt did not install it as part of vpackager's dependency.....and i just check gslapt there is no libffi.....
but if I run slapt-get and i can install the libffi.......:P
btw, thanks....
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on April 14, 2008, 04:37:32 am
libiffi is a dependancy for the gambas package, not for vpackager directly
Title: Re: The New vpackager Thread - take a peak
Post by: hata_ph on April 14, 2008, 06:43:19 am
libiffi is a dependancy for the gambas package, not for vpackager directly

shouldn't gslapt/slapt-get will resolve the dependency issue for it as vpackager require gambas2 and libffi is a dependency of gambas2?
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on April 14, 2008, 07:47:23 am
yes... it should.. the problem here is that we need an updated gambas2 package.

vpackager is being developed on 2.5, and the latest on our repos is 2.0 I think... so we're a little behind there...

Sorry for the inconvenience.
Title: Re: The New vpackager Thread - take a peak
Post by: MikeCindi on April 14, 2008, 09:45:12 am
2.5 is in the testing repository isn't it?
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on April 14, 2008, 10:17:59 am
2.5 is in the testing repository isn't it?
Not sure, I made a dirty build of on my box to continue the development because 2.0.0 had problem with the gtk component (used in vpackager)

when I do "slapt-get --search gambas2", only my dirty 2.5 build comes up
Title: Re: The New vpackager Thread - take a peak
Post by: uelsk8s on April 14, 2008, 01:33:35 pm
2.5.0 is in the testing repo.
Quote
root:# slapt-get --search ^gambas2
gambas2-2.5.0-i586-1vl59 [inst=no]: Gambas 2 - BASIC IDE for Linux
gambas2-runtime-2.0.0-i586-1vl59 [inst=yes]: Gambas 2 Runtime
gambas2-runtime-2.5.0-i586-1vl59 [inst=no]: Gambas 2 Runtime

maybe it is named the same as the one you built?
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on April 14, 2008, 01:54:32 pm
/me stands corrected

BTW, we will have a new version of vpackager coming up real soon... watch out for new features including dependancy resolving capabilities ;)
Title: Re: The New vpackager Thread - take a peak
Post by: hata_ph on April 14, 2008, 06:40:08 pm
yes... it should.. the problem here is that we need an updated gambas2 package.

vpackager is being developed on 2.5, and the latest on our repos is 2.0 I think... so we're a little behind there...

Sorry for the inconvenience.


is ok... :)
Title: Re: The New vpackager Thread - take a peak
Post by: MikeCindi on April 14, 2008, 07:42:49 pm
/me stands corrected
Looks like you're "sitting corrected" if your darkstar tux is any indication. :P BTW, thank you for the work you are doing on vpackager.
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on April 14, 2008, 08:07:04 pm
/me stands corrected
Looks like you're "sitting corrected" if your darkstar tux is any indication. :P BTW, thank you for the work you are doing on vpackager.

i cant say i dont enjoy developing the stuff. I think you guys are going to like the next release
Title: Re: The New vpackager Thread - take a peak
Post by: Dweeberkitty on April 15, 2008, 03:23:47 pm
i cant say i dont enjoy developing the stuff.

Hehe, those double negatives confused me for a second. I like vpackager a lot. I always recommend it to all people new to VL. Good job!
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on April 15, 2008, 06:03:43 pm
I appreciate that. Hopefully the next release will be more VL independent so other people running other distros can also use it. So far i've seen an increase in the number of .tgz downloads from the project page which could indicate that other people are checking it out as well
Title: Re: The New vpackager Thread - take a peak
Post by: M0E-lnx on April 29, 2008, 01:54:26 pm
New vpackager available... See here for the annoucement

http://www.vectorlinux.com/forum2/index.php?topic=6144.0

Title: Re: The New vpackager Thread - take a peak
Post by: uelsk8s on May 20, 2008, 07:08:40 am
The last vpackager will not finish building a package unless you have supplied a slack-desc file.
This is good and bad, I like making sure there is a description, but some people will just thing vpackager is broken.