I have misplaced my ssh keys, so I'd appreciate if one of the appropriate repo maintainers placed a copy of it in the correct section of the forums for this.

Notes about this release This release features the same backbone as the preceeding releases with a couple of exeptions.New features include

Dependency checking and resolving in the cruxports4slack gui

A fiew more windows have been made resizable for your viewing pleasure

The application now remember window sizes and position on the screen. This keeps windows from popping up all over your desktop

Look for many cosmetic changes all over the application

Another major change in this release:The package editing tool has been disabled.This is due to the lack of useage for this type of application and in order to concentrate development efforts on the most important and mostly used functions.The plan is to drop it unless the community asks for it.

How do I get it?http://vpackager.googlecode.comThe project page is the main source for the package until it gets put into the repositories. Please see the list of dependencies in the project page, all of them are available from the repositories. *** IMPORTANT *** Please upgrade your gambas-runtime package to version 2.5.0 and install libffi from the repositories.

This version of 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.

please,dont drop the package editor tool.. Can you sepparate it on a different project/application then?

<offtopic> im still around btw, just waiting for a vector release with xorg7.3 to come out so i can have another try to get wacom driver to build and work correctly on vector.The only thing thats stopping me from installing it again on my main machine.It seems that the driver wouldnt work with the xorg on vec59gold.does the light edition have a newer xorg? I will download it and install it right now if it does.Somebody has to build that wacom driver soon

the problem is a typo in the default config option that it passes,i guess..

this is vpackager on vl-lightrc1

i'm trying to build fbxkb...maybe its configure script doesnt support those options..

EDIT: aah,forget it,it can't even pass make..I'll do it with the console

it seems that vpackager gets some error during "make"... when i run make in the tmp directory where it is, it compiles without a problem... btw i packaged it...to whom do i have to send the package? I lost my ftp key

Been trying vpackage 1.0.12 (from help about, I'm sure it said 1.0.11 in repo) on VL5.9 standard and I seem to be having a few problems with it.

I'm using vpackage to compile fpm, all goes well with no errors but if I click on install I get the following error message:

[4] Not enough arguments. FrmBuildView.?.0

If I click on save instead then it tells me it will save in my home directory but the only file to be saved there is a script file. If I then look in the /tmp/vpackage/ the built package can be found. The built package seems to install and run OK so I think the actual compile and build is working OK.

Also installing vpackage 1.0.12 seems to break VASMCC which I guess is something to do with the packages that are updated during vpackage installation. VASMCC now gives the following error:

Please bare in mind that I don't really no what I am doing but then vpackage is supposed to make it easy for us noobs to make packages.

I have also tried all of the above on a clean install of VL5.9 standard with the same results. This post is to help the developers rather than being a request for help but it would be nice to know I'm doing something wrong. If you need more info just let me know and I'll do my best to help.

Thanks for testing...As you may know... I, El moe-dogg is responsible for both of those bugs!

I will look into the vpackager bug... I assume you have upgraded the binary as instructed previously, that's why you're seeing 1.0.12 and not 1.0.11. Meaning.. that the bug is still there... Will get it squared away.

About vasmCC...

It is possible that things broke because of the way vapckager used to ship (with needed libraries... ) whereas these libraries are now available in the repos as well..Make sure your gambas2-runtime is at version 2.5.0 or neweralso, make sure there is nothing in /opt/vpackager (if you have this, you need to remove this and remove the vpackager package, then re-install a new copy of vpackager)

I must apologies as I forgot to mention that I had indeed updated vpackager in /usr/bin as per your previous post. Too much wine I guess!

I have checked in /opt/ and the only things there are /opt/Adobe, /opt/kde and /opt/seamonkey. I have also checked the gambas version with Gslapt and this claims the following are installed: gambas-runtime 1.0.19-i586-1vl59 gambas2-runtime 2.5.0--i586-1vl59

Out of interest I have tried just installing gambas 2.5.0 on a fresh install of vl5.9 standard and that breaks vasmcc although this time it just doesn't start with no errors reported. If I then remove gambas 2.5.0 vasmcc then works again. One thing I noted is that when I select gambas 2.5.0 for removal Gsalpt automatically selects vasmcc 1.0.12, vpackager 1.0.10b and 1.0.11 for removal even though they are not installed. I have done this on a separate partition so my main partition is unaffected so as before this is for information rather than a request for help.

1. When one creates a slack-desc file, it starts with blank fields and just the name of the program. The problem is after hitting save and continue, if then I want to make amendments to the slack-desc file (and click the button again) I get all the fields blank again. The same goes for previewing or slightly changing a previously formatted file. I guess it would be nice if the "new description" button was actually for "new or 'current' descriptions"

2. I compiled a program with customized configure options and build flags. While the configure options are correct in the slack-desc file, the build flags are written as the default ones.

3. Related to the above, it would be nice if the outputs during the process (and the log file) contained the commands that are being used. That way, one could double-check the ./configure options and build flags while it is running, or later see what was used just by opening the log file.

4. Vpackager told me that the package was saved in my /home directory (I guess because that's where the compressed source was), but there was no copy there. It was only in the temporary directory.

Can I PLEASE get you to file a bug report for me at the project page?That will help a lot... Thanks for testing.... When you're writing code and trying to test the stuff at the same time you tend to go right past little important details like that

Please do me a favor... fill out the bug reports at the project page.... please.. I have taken a heavy load with vasmcc as well... these bug reports at the project page will help me get to the right place when I start debuggin...

Thanks

EDITWell, I've made a couple of entries myself for these bugs... so I can come back later and work on them..

But regarding your 3rd issue.In the 1.0.12 release (not released yet) I have enabled the build script writer function. This will generate a script with all the commands necessary to build the same package using whatever the user input was for that one application.Also, in that release, before the build process begins, vpackager will play information such as application details, CFLAGS to be used, configure options and stuff like that.