Making packages without using the wok

SliTaz Forum » English Support » Live and installation

Making packages without using the wok

(42 posts) (5 voices)

Started 8 years ago by linuxscripts
Latest reply from linuxscripts
This topic is not a support question

Tags:

No tags yet.

« Previous 123 Next »

Aleksej

offline
Coder-hobbyist

Hi Darjeeling,

CSUM=$(find $SDIR/$PNAM/fs -type f -exec basename {} \; | md5sum | cut -d " " -f 1)

No, sorry, your oneliner shall not function as you want it.

First part
find $SDIR/$PNAM/fs -type f -exec basename {} \;
will print file names only. Without paths. Without date/time. Without their checksums.

What about links? Seems you don't want to list folders, but also you forget about links (also called symlinks, hardlinks).

What about order of printed files? If my memory serves me well, output by default based on the file change date.

Did you tried solution I posted for you (to change small "a" into big "A") here: http://forum.slitaz.org/topic/tazpkg-beta-needs-testing/page/6#post-41008 ?

--------

I confirm that "tazpkg pack" changed the time stamp of the folders. It not harms commonly, but it is a bit weird. I'll look what can cause this behavior.

Posted 8 years ago #
llev

offline
Member

@ linuxscripts
In addition to what Aleksej wrote:
- wok does not store packages, look by yourself: http://hg.slitaz.org/wok/file/c7a23f0fad68 (where did you find that Hg is a package server?)
- if you make your own packages, get-* commands and the like have no reason to be in your receipt
- tazpkg has a mechanism to manage config files (read the doc), but anyway you'd rather use post_remove

Posted 8 years ago #
Darjeeling

offline
Member

Hi Aleksej,

You have convinced me! I'm going to use your 'formula' because it's more universal than what I have come up with last week, which works too, but only produces an md5 of all the files in the tree. Of course, my first solution was even more universal but didn't work because of the changing directory dates.

But if you knew ... except for the local mirror (which I never touch) I'm only maintaining 4 lousy packages (lxpanel, opera, redglass, spacefm) and until not too long ago there never was any integrity check for them. Some weeks ago I put in a simple file count/comparison, to make sure. And then it all got a bit out of hand just before Christmas when I wanted to have something more fancy than this and began tinkering with an over-all checksum using ls, tar, find ... But that's over now as your solution works well and is even shorter than mine.

P.S.

Regarding symlinks ... there aren't any in my packages as I prefer to create them post_install() out of the recipe, which I think is safer. For each of the 4 packages I have a script that does everything: download (lxpanel, spacefm), compile & make (spacefm), create/modify the package tree (lxpanel, spacefm) create the recipe and run tazpkg (all 4 of them) and copy the package to my makeCD directory. It works well but I've spend a lot of time on this (and learned a lot).

Posted 8 years ago #
llev

offline
Member

Regarding symlinks ... there aren't any in my packages as I prefer to create them post_install() out of the recipe, which I think is safer.

I don't see how it can be safer, but I see how it can be bad :) : if another package X has a file or link at the same place, your package will not be recorded by tazpkg as a modifier of X, and if you remove your package, X should be reinstalled but won't be.

Aleksej worked very hard on such subtle cases, now tazpkg takes care of them!

Posted 8 years ago #
linuxscripts

offline
Member

I'm sure, you know what your command "cd ~/usr/bin" means :-D
Your home folder contains subfolder "usr", and this, in turn, contains "bin". But it's weird, isn't it?

Sorry for that; it needed to be cd /usr/bin, not cd ~/usr/bin. I copied over a command I wrote a while back, before llev mentioned what the ~ does

cd /usr/lib/X11/app-defaults/XScreenSaver/
Weird, according to [1, 2] this path is... file, not a folder. You can't cd (change directory) to the file; you can change directory only to directory.

Made a mistake there as well; I thought xscreensaver (file) was in XScreenSaver folder, but that was incorrect (was directly in app-defaults) ; so deleted the extra folder and remade the package.

Function "genpkg_rules()" will never be called since you not using the "official way" of making the SliTaz packages, and you free, truly, to put here what you want... But you have been warned ;-)

If genpkg_rules(), as well as post_remove I assume ? are never called when packed using tazpkg, there's no point in me adding them at all. Can you tell me how I do need to include commands (under the tazpkg-package method) so they are executed ? Also, what's the "official way" of packing using tazwok; ie what commands are needed for this, and/or is there a manual (I always read the man pages, and also read http://doc.slitaz.org/en:cookbook:wok, but that didn't help me (only the making of a "personal wok" is briefly explained, not the way to build packages suitable for upload to the slitaz server))?

Please, put your packages to the one of the File Sharing services, and put here links, so I can download, and extract your packages.

As mentioned, I've been putting my packages at https://drive.google.com/drive/folders/0B0Orq8VMiN7QMndGZndMTTl5a0E
It should be downloadable using firefox/pale moon (not sure about xombrero/tazweb).
I'll mail them to you as well.

Perhaps you can improve the description file of at least 1 of the packages (ie gajim-OTR) so I know how to make the commands executable, and can finish the rest of the first batch of packages ?

Posted 8 years ago #
linuxscripts

offline
Member

@llev

wok does not store packages, look by yourself: http://hg.slitaz.org/wok/file/c7a23f0fad68 (where did you find that Hg is a package server?)

Having read http://doc.slitaz.org/en:cookbook:wok which mentioned "wok-undigest: contributions awaiting testing/bug-fixing for inclusion in the unstable Wok", "wok: packages for the unstable, Cooking release", "wok-stable: packages for the stable SliTaz release" I thought there was a system in place for people to upload their packages (wok-undigest), and which then get reviewed (wok-stable). I was probably wrong here.

if you make your own packages, get-* commands and the like have no reason to be in your receipt

Yes, I normally wouldn't implement these, but the package you referred to was intented to work in conjunction in conjunction with the get-palemoon package (allready present on the slitaz servers).

Posted 8 years ago #
Darjeeling

offline
Member
Re: llev
> Aleksej worked very hard on such subtle cases ...

I agree and his work is much appreciated. But what each of us is doing really cannot be compared. Aleksej's work ends up in a public place for everybody to use while my stuff is private and geared towards a very special case scenario:

A shitPC that's only got a 1 GB hdd which is 25+ years old and extremely slow. And since the shitPC's mobo doesn't allow USB boot, a proper installation of SliTaz is impossible. So, I'm creating my own customized Live CD from justx rolling which has persistence for a number of important files and directories and, to make the whole set-up a bit more flexible, additionally pulls in a number of configuration files on each boot, so I don't have to burn a new CD for every little change. The trouble is that the hdd is rather full and that occasionally I have to juggle stuff around or "tar-up" things and store them temporarily on an external ntsf-formatted USB drive. On such occasions it has happened at least once that through my own negligence (or stupidity) I have broken some symlinks. This is why I'm now creating the package symlinks post_install. For my set-up this really is safer. I also don't see how these symlinks could ever get in conflict with other packages since they are purely internal, that is, inside the package's own tree (redglass and opera). The one exception is spacefm where I'm doing this in the receipt ...
```
post_install()
{
   cd /lib
   ln -s libudev.so.0.13.1 libudev.so.1
   ln -s libhistory.so.6.3 libhistory.so
   ln -s libhistory.so.6.3 libhistory.so.6
   ln -s libreadline.so.6.3 libreadline.so
   ln -s libreadline.so.6.3 libreadline.so.6
}

pre_remove()
{
   cd /lib
   rm -f libudev.so.1
   rm -f libhistory.so
   rm -f libhistory.so.6
   rm -f libreadline.so
   rm -f libreadline.so.6
}
```
... which was/is necessary (udev, bash) and has been working well since almost a year. But I haven't checked yet, whether I still have to do this.
Posted 8 years ago #
llev

offline
Member

@Darjeeling: you're very brave to make this PC work!
I mentioned this just in case, I was not teaching you a lesson :-)
As for the specific links you make, I wonder whether this could be done automatically by ldconfig?

Posted 8 years ago #
llev

offline
Member

@linuxscripts

Not sure, but I think you don't clearly see the difference between those three tasks: building, packing, installing. Do you? In the page you cite, maybe read again the first paragraph. Did you also read the section on receipts, in the Cookbook? This will explain the use of the various functions.

The phrases you cite are a shortcut, they should read "[receipt and extra files needed to cook] packages..." You should also read the documentation of TazPkg and Cookutils (they come with the corresponding packages).

HTH

Posted 8 years ago #
sixofeight

offline
Member

@ Darjeeling
--> the shitPC's mobo doesn't allow USB boot <--
Have you already tried the "plop" Bootmanager?
(fits on a 3.5 floppy / or CD etc.)
most of old PCs boot then usb-flash-drives.
https://www.plop.at/en/bootmanagers.html

Posted 8 years ago #
Darjeeling

offline
Member

Re: llev
> ... you're very brave to make this PC work!

Hahaha! It's actually my girlfriend's PC. I would never have bought such a pile of trash: 3rd mobo, 3rd power supply, hdd gone, all in just under 2 years! This was 6 years ago just about the time when 3.0 came out. To console her for all the trouble a computer shop guy gave my girlfriend a "10 GB" hdd for free which on closer inspection turned out to be a 1 GB Seagate drive from the Pleistocene of computing. Still, I got ambitious and instead of buying a new hdd I've been working, improving and learning ever since. Personally, I very much like the static nature of this set-up which except for its abysmal boot-up time (3+ minutes) performs very well, is fast, safe and practically incorruptible.

Regarding ldconfig ... I've never used it but I just read its manpage. Interesting, but at this moment I'm battling on so many fronts (X, packaging, spacefm, panel config, /applications, /icons etc.) that I don't want to open another can of worms :-) In the manpage it says that ldconfig maintains a cache of links to shared libraries which probably doesn't lend itself well to a static installation like mine. Would I have to include this cache in my persistent storage? Anyways ... I'm sure I will try out ldconfig some time.

Re: sixofeight
Yes, I have heard and read about Plop. But I've never tried it out and I have no idea what trickery it is that makes this work. Are you using it? Of course it would be great if I could boot from an USB stick or from one of our external USB drives. Now that you've reminded me of Plop I will definitely try to make it work as soon as I have taken care of a few other issues. At this moment there's "Baustelle" all over the place and I don't want to start something like this before I have finished some other work.

Posted 8 years ago #
sixofeight

offline
Member

@ Darjeeling
Yes, I use plop and there is no risk at all to do so, because this tool doesn't install,(but of course one can install it), or overwrite something.

btw
I also use porteus, another relatively small (~200mb) Linux live distro which has "plop" as an option at the boot screen.
(plug in the usb > boot the porteus CD > at the boot screen select plop and boot the usb-flash-drive)
...work flawlessly...

Posted 8 years ago #
llev

offline
Member

@Darjeeling

ldconfig does two things: maintain a cache, and create symlinks. You can disable the former with -N:

-N
Don't rebuild the cache. Unless -X is also specified, links are still updated.
-X
Don't update links. Unless -N is also specified, the cache is still rebuilt.

I also used Plop bootmanager in the past. This was a PIII laptop with USB 1.1 ports; I had trouble with the optical drive, but the laptop came with a USB floppy drive (from which the BIOS allowed to boot). You can see Plop as a bootloader/chainloader with additional drivers.

Posted 8 years ago #
linuxscripts

offline
Member

I've been re-reading things and trying to figure out how to make the commands work, but I just don't see how to do it. I did read the section on receipts, in the Cookbook, as wel as the tazpkg manual and cookutils manual, but that didn't help.

Besides not understanding how to make the commands work at all, I also don't see a way around the timing issue I mentioned (ie that some commands need to be executed before some files are overwritten, ...) or that some commands need to be executed first before files are copied in, ...

Can you give me a working version of the gajim-OTR receipt, so I can see how *I should* do it ? Here's the latest version of the receipt (updated it as it needed some commands afte all):

# SliTaz package receipt.
PACKED_SIZE="112.0K"
UNPACKED_SIZE="396.0K"
PACKAGE="gajim-OTR"
VERSION="0.14.1"
CATEGORY="network"
SHORT_DESC="Adds the OTR (off-the-record) plugin to gajim"
WEB_SITE="https://trac-plugins.gajim.org/wiki/OffTheRecordPlugin"
MAINTAINER="teamtaz@slitaz.org"
DEPENDS="gajim"
CONFIG_FILES=""

# Rules to gen a SliTaz package suitable for Tazpkg.
genpkg_rules()
{
tazpkg get-install pycrypto

cd /usr/share/gajim/plugins/pure-python-otr-master
sudo python setup.py install
}

pre_remove()
{
cd /usr/share/gajim/
rm -rf plugins

tazpkg remove pycrypto
}

PS: In the event I'm unable to figure things out the correct way, one alternative I could do is just make a mere script and add that in the fs folder (for example under /home/tux/package_scripts/). People would then be able to execute my commands by running that script which copies itself immediatelly to the folder mentioned on the harddisk. If possible, I'd like to avoid this though and just use the correct way to do things.

Posted 8 years ago #
llev

offline
Member

Again, you're mixing package generation and installation. Installation is just a matter of copying the files which have been placed into the package when it was generated.
http://doc.slitaz.org/en:cookbook:receipt#functions

I can't help you with writing a correct receipt if you don't tell me exactly what you want to do.

Do you want the package built by the cooker? -> A
Or do you provide all the needed files in a tarball? -> B

A: What are the commands needed to compile the package (i.e. to produce the needed files)?

A&B: Give me the list of the files to install.

Posted 8 years ago #

RSS feed for this topic

« Previous 123 Next »

Reply »

You must log in to post.