TazPkg Beta needs testing

SliTaz Forum » Community Groups » Devel

TazPkg Beta needs testing

(94 posts) (12 voices)

Started 9 years ago by Aleksej
Latest reply from Aleksej
This topic is closed
This topic is not a support question

Tags:

No tags yet.

12…7 Next »

Aleksej

offline
Coder-hobbyist
Hi there! :)

I just released new TazPkg Beta.
I invite everyone who cares about the fate of SliTaz to the testing.

It is a separate package called "tazpkg-test"; let the original "tazpkg" be a sort of stable while we trying new code.

You'll get the package on the "Download" link on this page. Double click downloaded package to install it.

I know this TazPkg release is Beta state, and it still have few FIXMEs and TODOs. I'll try to solve it in a near future. At least this TazPkg can download and install packages :D

What to test? Everything. Read the documentation (yes, it's too large now) and try all the commands and options you've found there. Try the "cold" packages installation (when some package installed in a first time) and "warm" packages re-installation (upgrade).

Proof-read the documentation. Rephrase it to easy reading. Translate it to other languages you know.

Now you can use "--root" option for all TazPkg commands. You can specify real Rolling installation to work with. Or you can specify new non-existing folder, and TazPkg recreates its infrastructure there. For example:
```
$ su
# tazpkg -gi nano --root=/tmp/test
```
After that you'll get:
- /tmp/test/etc/slitaz/: configuration files for this "root";
- /tmp/test/var/lib/tazpkg: brand new TazPkg Databases for this "root";
- installed specified package "nano" and all its dependencies (glibc-base, ncurses-common, ncursesw, and zlib);
- /tmp/test/var/log/slitaz/tazpkg.log: log of TazPkg actions;
- … and number of the other great stuff :D
It is deep night here right now, I went to sleep.
See you all!
Posted 9 years ago #
az_ua

offline
Moderator

rolling-core "2015-10-04" iso

# tazpkg -gi locale-ru

Installation of package "locale-ru" ================================================================================ Russian locale pack -------------------------------------------------------------------------------- Copying package... [ Done ] Extracting package... [ Done ] Remember modified packages... [ Done ] Installing package...cp: can't stat 'fs/usr/share/lxpanel/images/xkb-flags/ua.png': No such file or directory cp: can't stat 'fs/usr/share/lxpanel/images/xkb-flags/ru.png': No such file or directory [ Failed ] Removing all tmp files... [ Done ]
# tazpkg -gi locale-ru --forced ... ... Installing package... [ Done ] ... ...

Posted 9 years ago #
Aleksej

offline
Coder-hobbyist

Thank you, Alexander!

So, here is a wide problem with all sort of symlinks, both folders and files.
Do we have Busybox's cp properly worked? Can you retry with the GNU Coreutils version of cp?

Package installation is a simple single command, and I not changed it.
Note, if you wanted to use Coreutils cp rather to Busybox cp now you need specify the full path to cp command; or remove cp from the alias-make loop in the "getenv" module: /usr/libexec/tazpkg/getenv somewhere at the script's begin ( modules are minified).

Posted 9 years ago #
Aleksej

offline
Coder-hobbyist

Hi there!

Trying to solve nasty behavior with copying "real" folders into "symlinked" folders I upgraded TazPkg-test. Download: http://cook.slitaz.org/cooker.cgi?download=tazpkg-test-845.tazpkg

While we can't copy directories into symlinks, I wanted to copy directories into directories (symlinks destinations directories). Here small picture describing how I rebuild package's directories before installing them into filesystem:

It works. Please testing.

Posted 9 years ago #
llev

offline
Member

Hi Aleksej,

0) This is a huge piece of great work!

1) The --root option is a great idea; is it possible to install tazpkg-test itself into a test dir? Maybe do I just need to change the "sourcing" commands like . /lib/libtaz.sh to . /mytestdir/lib/libtaz.sh? (I would unpack tazpkg-test by hand into /mytestdir.)

2) Your solution for the linked dir problem is very elegant (in your example file4 and file5 should be under lib3/, no?). But I'm wondering: if we remove the previous package that created the link /lib/lib2 -> /usr/lib3, do we remove the link? Because then the software that looks for file12 in /lib/lib2 would fail.

3) The "compiled" scripts are unindented (probably a side effect of comments removal?), which makes them very hard to read... Can this be changed? Well, I guess users don't read the script, and devs use the source. So next question:

4) Can you tell me how to download the source tree?

Thanks!

Posted 9 years ago #
Aleksej

offline
Coder-hobbyist
Hi llev,

This is a huge piece of great work!

Thank you! It is all just for fun :) I just like to develop and to solve our development problems… I'm 39 and I think I need to train my brain on a daily basis :)

The --root option is a great idea

This is an old idea. And it was not properly integrated into existing TazPkg code. Some commands was supported this option, other — don't. Now all commands are supported --root option.

is it possible to install tazpkg-test itself into a test dir?

Oh, I not asked yet myself is it possible.
Currently, "tazpkg-test" package overwrites all the files of regular "tazpkg" files.
Tester can return back to using "tazpkg" using next commands:
```
# tazpkg get-install tazpkg --forced
# tazpkg remove tazpkg-test
```
Current Makefile defines few variables with the default values, and you can tweak these variables:
- Regular installing TazPkg from sources:
  make; sudo make install; make clean
- Tweak variables (only example):
  
  make prefix=/usr/local sudo make prefix=/usr/local install make clean
Maybe do I just need to change the "sourcing" commands like . /lib/libtaz.sh to . /mytestdir/lib/libtaz.sh?

Completely no; libtaz.sh is not a part of TazPkg, it is wide-used system library. Leave it itself.

I would unpack tazpkg-test by hand into /mytestdir.

So, now you have... ? —
- /mytestdir/usr/bin/tazpkg
- /mytestdir/usr/libexec/tazpkg/block, etc.
You need to find hardcoded paths in the TazPkg "compiled" files pointed to "/usr/libexec/tazpkg" and to point them to the new place ("/mytestdir/usr/libexec/tazpkg" in your case). You can use command line to do it:
```
find /mytestdir -type f -exec sed -i "s|/usr/libexec/tazpkg|/mytestdir&|g" \{\} \;
```
in your example file4 and file5 should be under lib3/, no?

Yes. You can find them both in the "/lib/lib2/" and "/usr/lib3/".

But I'm wondering: if we remove the previous package that created the link /lib/lib2 -> /usr/lib3, do we remove the link? Because then the software that looks for file12 in /lib/lib2 would fail.

I'll screw my brain with these symlinks too soon :D

There are exists "regular" files and "regular" folders. TazPkg stores information about installed files only. And it will remove only installed files while you remove the package. In addition it will remove all empty folders (where files was) up to first non-empty folder. It will not remove "/usr/lib3/" if it still contains files. But…

There are exists "weird" symlinks! Symlink is a file. But it can point both to file or folder. And there is no easy answer to question "is TazPkg stores symlinks to folders in the files.list?": I need to see it. And I can't answer to your question: I need to make few tests. I'll prepare test packages and will install them and will remove. Better if I can find real packages with the described case.

The "compiled" scripts are unindented (probably a side effect of comments removal?), which makes them very hard to read... Can this be changed? Well, I guess users don't read the script, and devs use the source.

There are removed all comments and indentations from scripts. Yes, it is hard to read, but you not need to read this (something similar you'll find in our init script :D ). Scripts worked well without comments and indentations, as well as with, but it saves us few kilobytes. Idea is: if you need to develop TazPkg please use sources. There you'll find extended comments and all developer needs.

Can you tell me how to download the source tree?

Source code repository for TazPkg is http://hg.slitaz.org/tazpkg/ (please follow link)
Look at the top — here you'll see:

Project: tazpkg

Clone project: hg clone http://hg.slitaz.org/tazpkg

Download tarball: bz2 gz

If you need to download sources one or few times only — you can download the tarball in tar.bz2 or tar.gz format (and then reload it when it changed).

If you need to download sources on a regular basis —
1. Install Mercurial:
  # tazpkg -gi mercurial
2. Go to your folder for source codes using terminal.
3. Execute command (as regular user) to initial clone the repository:
  hg clone http://hg.slitaz.org/tazpkg
4. You'll find new folder "tazpkg" in your folder for source codes. This folder will contain current TazPkg sources.
5. Next, when you need to update sources from repository, issue a command (as regular user) within this "tazpkg" folder:
  hg pull -u
Thanks!

Thank you for your interest!
Posted 9 years ago #
llev

offline
Member
Hi Aleksej,

Thanks for the explanations. Silly me, I went to hg but did not see the tarball links.

Also I had not thought of using the "prefix=" argument of "make", this is much simpler than editing the paths directly in the compiled scripts!

About links. Maybe something like this in remove_with_path():
```
if [ -L "$1" ]; then
  target=$(readlink -n "$1")
  if [ -d "$target" ] ; then
    {while-loop to remove dirs}
    [ -d "$target" ] || rm "$1" # if target was removed, remove link
    return
  fi
fi
```
Small problem: if file12 is alone in /usr/lib3, and files.list shows /usr/lib3/file12 *after* /lib/lib2, $target is not empty when /lib/lib2 is examined so the link is not removed.
So this is not clean, but it is better to leave a broken link that no software uses, than to remove a working link on which some software relies!
Posted 9 years ago #
Aleksej

offline
Coder-hobbyist
Hi llev,

Sorry, I not executed any tests yet.
Just info for thought:
1. When TazPkg packed the package, it builds the list of files in this order: "regular" files then symlinks: http://hg.slitaz.org/tazpkg/file/8a73a58ed3cb/modules/pack#l28
2. And the same behavior when Cook prepared the files.list: http://hg.slitaz.org/cookutils/file/e0a7dfab950c/cook#l812
First case when you build your own packages using TazPkg. Second case for all official packages.

Small problem: if file12 is alone in /usr/lib3, and files.list shows /usr/lib3/file12 *after* /lib/lib2, $target is not empty when /lib/lib2 is examined so the link is not removed.

As /lib/lib2/ is a symlink, then it will be listed after /usr/lib3/file12.

So…? Any problem?
Posted 9 years ago #
llev

offline
Member

So... sounds great! Looks like this approach would work. Time will tell...

Posted 9 years ago #
llev

offline
Member

I've just found there's a "mkdb" function. "usage" doesn't show it, is it on purpose?
How does it work?

Posted 9 years ago #
llev

offline
Member

Updated fr.po for tazpkg-beta: http://www.cjoint.com/c/EJjuDImN0fA

Posted 9 years ago #
Aleksej

offline
Coder-hobbyist

Oh, really. This "mkdb" function is a very new, and is absent in the "usage" list and in the documentation.
Please read comments in the "mkdb" module for more information. And I'll update "usage" and docs soon.

Also thank you for translation. I'll push it tomorrow to the sources.

Posted 9 years ago #
Aleksej

offline
Coder-hobbyist

Hi,

Add 'mkdb' description to 'usage' and English docs. Refresh French translation (thanks Lucas Levrel)

http://hg.slitaz.org/tazpkg/rev/e54a3ba8cc25

Posted 9 years ago #
llev

offline
Member

Nice! Now the pot&po files need to be updated to include the new string. Should I do: make pot && make msgmerge? Or should this be done on the Hg server?

Posted 9 years ago #
Aleksej

offline
Coder-hobbyist

Should I do: make pot && make msgmerge? Or should this be done on the Hg server?

You may make it "in advance", in belief developer will make the same changes.
Hg server is only a storage.

First, we make changes to code, and maybe to translations. Then bug fixing and new features implementation. After that developer make pot and msgmerge (note, make pot and msgmerge produces large nearly "senseless" commit, so developers not to like to update po files frequently).

Please, push me when I need to rebuild pot and po's.

Posted 9 years ago #

RSS feed for this topic

12…7 Next »

Topic Closed

This topic has been closed to new replies.