packaging

[luddite]

Re: packages I just installed salixos from the live cd, just got internet connection & fancied seeing what extra packages I could get.

I've looked at the faq and understand that I can't use packages from linuxpackages.net, nor use slackpkg. Gslapt came up ok and I have installed slapt-src, but couldn't see sourcery anywhere.

Slapt-src is working( at least was while typing this ) ,and it partially installed gcompris ,although I can see its listed in Gslapt gui,

just used slapt-src –search gcompris, and slapt-src –install gcompris:8.4.12, but can not understand
that slapt-src –search sourcery didn't find anything. Other question is , do I have to edit any file
for mirrors for slapt-src to check slackbuilds.org, or does slapt-src check that repo automatically.

Ps got this error using slapt-src to install gcompris :
texi2html -monolithic gcompris.texi
make[3] : texi2html : command not found
fakeroot –sh gcompris.SlackBuild Failed

[tsuren]

sourcery comes with 13.37. And salix os live 13.37 in not out yet. So the options you have is to upgrade your system to 13.37 (follow the wiki on how to do this), or to install it with the standard installation CD.

or you can download sourcery from here.

slack.builds do not take care of dependencies, so you have to take care of that yourself. You can also just download build codes and create the corresponding packages yourself.

[mimosa]

Welcome to Salix!

The version of that application from src looks like it's older. Probably better to install from Gslapt, and you shouldn't have any dependency problems - which is what that message looks like, in which case, you would need to install texi2html first, then try the main app again. But that's just a guess. Anyway, in this case, what you want is available in the standard repos.

Sourcery is the graphical version of slapt-src, available from the System menu. Sourcery is to slapt-src as Gslapt is to slapt-get, and it is already pointed at http://www.slackbuilds.org.

Try slapt-get --search sourcery. But it should already be installed, if you are using the latest version of Salix.

Ah, but if you're using a live cd, you can't be (it hasn't been released yet). Sourcery is only available in Salix 13.37, the non-live versions of which are available for download. Live probably coming soon!

[luddite]

ok thanks for replies ,

just downloaded xfce 13.37 so will install that over the installed live version; this is best option since i have quick internet away from salix pc and slow internet where salix pc is.

one other question .

I've had a look at slackbuilds.org and understand installing these packages with sourcery won't be a problem. now i would like to learn the nitty gritty, and understand the basics, that if you manually download a build script for a package containing, " somepackage.SlackBuild , slack-desc etc" and you unpack it getting a directory called say "somepackage", and you put the downloaded source code into this "somepackage" directory then $ cd somepackage,

and then # ./somepackage.SlackBuild

apart from there being be some dependency issues that would need sorting , apart from that , would this be a correct way about creating a
package ? This would be a good option taking into account I can easily download anything awayfrom the computer whith salix on it, and unfortunately
the salix pc has access to only slow internet facilites.

[gapan]

would this be a correct way about creating a
package ?

Of course.

[john256]

Thanks to gapan[1], I also discovered the beautiful simplicity of using a dedicated SLKBUILD file to create packages.

[1] http://www.salixos.org/forum/viewtopic. ... 391#p14992

[luddite]

cheers all

at lesat now have 13.37 xfce installed over the live cd install , noticed openoffice has been dropped for libre, also now can see sourcery - very impressive list!

john256 cheers , that link is about updating a package when you already have it , haven't done that process yet , or read up on it - first question off top of my head would be version , i guess you get new source then edit the slkbuild file in /usr/src/package to match version of source , although the presence of $ is confusing to me at present.

Obvious to some probably most ,but to me Linux is an exponential line, with the elevated bit seeming to be the height of Mount Etna!

[john256]

...
john256 cheers , that link is about updating a package when you already have it , haven't done that process yet , or read up on it - first question off top of my head would be version , i guess you get new source then edit the slkbuild file in /usr/src/package to match version of source , although the presence of $ is confusing to me at present.

In my case I already had installed the package from the repo, but this is not necessary when using the provided SLKBUILD file to create your own package. In my case all I had to do was to copy the provided files into a build directory, to change the variable "pkgver=2.12.1" (located near the top of the SLKBUILD file) to "pkgver=2.13.0" and to start the building process from within the build directory. The sources are downloaded, if not present in the directory, and a package is created. Elegant and easy

[luddite]

cheers john256

sometimes its the simple things in text which confues me, such as sometimes text includes "foo" & "bar" and I never know when text is literal or repsents something ,

thus is i'm assuming "newpackage" is to be literally and does what it says on the tin is code to produce a new package ?




cd /usr/src/R-2.12.1
vi SLKBUILD
slkbuild -X
spkg -u newpackage.txz

[mimosa]

In this case you have to replace it with the name of the actual package you have just created.

What tells you this is that it's the name of a file to be installed. If you installed 'newpackage.txz' every time, you would always be installing the same package (supposing it existed), not the new one you made.

Try entering it as it is; I bet it'll say "No such file" or some such.