I decided that it will be mighty nice if there's such a thread.So even people who dont have ftp/ssh key,would be able to submit their port scripts and others test them.

A cruxports4slack script is like a SLACKBUILD script that automates the compiling and packaging process (adding slack-desc and slackrequired) , but with the advantage of downloading its source code automatically too. So if you would like to compile a newer version of something,you would only have to run vpackager-->cruxports4slack (gui frontend+modified cruxports4slack) and you would get a list of avaiable scripts from crux repositories and VL's official ports repo.To make it download and compile a newer version,you would only have to make a simple modification to the avaiable script (like change the $VERSION variable).

These scripts are made in a manner thats really easy to modify- you would only have to put the right variables for the software you need in most cases.

If you have written a script,or would like to try,why not post it here (put quote or code tags please)

then we will remove the sed line that removes access to the help files.and finally we remove the "rm -rf $PKG/usr/share/{gtk-doc,locale}" line that removes the docs from the package.Below you have a fixed gimp Pkgfile that make the latest gimp package.

Edit:this is weird,but a segfault crash happens if you run guatu from the terminal and open an archive.Also guatu is stable and useable if you install glitz,before compiling it.At their website or configure script glitz wasnt included as a must,but i noticed that its terribly buggy if you dont have it installed! Glsapt glitz before trying to install guatu,or you get a faulty compile!

I'd say: this thread+ file>new script or File>open pkgfile function in vpackager would make installing from source a pretty fun thing to do.

My question now is: can we somehow include the slack-desc inside the script, how exactly.I would like to see a script that does that. Can we copy the contense of an existing slack-desc into the ports script?

another question: Where does vpackager put the built from pkgfile package? I cant find it at tmp it seems.EDIT: ok i found it. Why are they stored at such unconvenient places?

I would love to submit the packages as well,but i cant seem to find them (have to rebuild?) and i lost my ssh key.I'll have to generate a new one and mail john again

My question now is: can we somehow include the slack-desc inside the script, how exactly.I would like to see a script that does that. Can we copy the contense of an existing slack-desc into the ports script? Cool

My question now is: can we somehow include the slack-desc inside the script,

No. It can't work the way the script is currently written. If you manually copy the slack-desc to a created install dir. Or embed a slack-desc into your Pkgfile (using cat), it will be overwritten by the pkgfile script when attempting to use the description line to create a new slack-desc, or if existing slack-desc is detected in dir the script was launched from.

That really is interesting kidd. What is happening is the script IS finding your slack-desc, then copying to install/slack-desc. Then the build info is appended to the new copy in install/slack-desc. Then your original is overwritten by the appended copy in install. It's odd it's not being included into the package.

Just for the heck of it can you try adding --requiredbuilder when launching the script? This will cause the script to use requiredbuilder and makepkg rather then use the default makeslapt.

I gave it a bit of thought. It is possible to include the slack-desc within the pkgfile. Here's a example using a recent slack-desc of mine.

Quote

cat > $CWD/slack-desc << EOFcompiz: compiz (OpenGL window and compositing manager)compiz: compiz: Compiz is an OpenGL compositing manager that usescompiz: GLX_EXT_texture_from_pixmap for binding redirected top-level windowscompiz: to texture objects. It has a flexible plug-in system and it iscompiz: designed to run well on most graphics hardware.compiz: compiz: compiz: License: GPL LGPL MITcompiz: Author: David Reveman <davidr@novell.com>compiz: Website: http://www.compiz-fusion.org/EOF

This will create a slack-desc in the directory the script was launched from. The the pkgmk script "should" find it there and then copy it over to /install/slack-desc.

Kinda goofy, but it should work. Might just as well add another dozen lines and make it a full blown .SlackBuild while your at it

Edit: Another thought kidd.... the first word of each line of the slack-desc must be exactly the name of your package, and it is case sensitive. For example package: foo-1.2.3-i586-1vl59.tlz would have foo: and a space at the beginning of each line. Forgive me if I insulted, but sometimes it's easier to start with the basics when trying to figure these things out.

BUILDDATE: `date`PACKAGER: $VL_PACKAGER.....info and copied back to $CWD, but the package seems to build without that info... it's really strange.

Another strange thing. If you pasted the above text from your appended slack-desc... something is wrong (nothing you've done). date and $VL_PACKAGER should not be seen. It should be today's date and your name. Something like this.

This program tries to accelerate the downloading process by using multipleconnections for one file. Starting from version 0.97, the program can usemultiple mirrors for one download as well. The program tries to be as lightas possible (25-30k in binary form), so it might be useful as a wget cloneon byte-critical systems.

axel: Axel. A light download acceleratoraxel: axel: This program tries to accelerate the downloading process by using multipleaxel: connections for one file. Starting from version 0.97, the program can useaxel: multiple mirrors for one download as well. The program tries to be as lightaxel: as possible (25-30k in binary form), so it might be useful as a wget cloneaxel: on byte-critical systems.axel: axel: Website: http://wilmer.gaast.net/main.php/axel.htmlaxel: Author: Wilmer van der Gaast <lintux@debian.org>