closed not a support question
llev
offlineMember
Can you simplify the algorythm?
Not the algo which finds unique dirs, for sure. But the "remove empty parents" thing is implemented in rmdir:
@@ -166,11 +166,7 @@
debug 'Removing folders...'
for dir2r in $(cat "$dirs2remove"); do
- dir="$dir2r"
- while [ -n "$dir" ]; do
- rmdir "$dir" 2>/dev/null || break
- dir="${dir%/*}"
- done
+ rmdir -p "$dir2r" 2>/dev/null
done
rm "$files2remove" "$dirs2remove"
unset IFS
Aleksej
offlineCoder-hobbyist
Lucas,
I need to test it. Looks great.
Darjeeling,
Yeah, really misunderstanding :(
Please, boot this original unaltered SliTaz Rolling ISO! Please, select different flavors: base, justx, gtkonly, core. Every time, please check the content of /var/lib/tazpkg (hint: it's 247 packages for Core, about 150 packages for Gtkonly, a very handful for Base, and so on). Please, check that Gtkonly has yad and xorg-xsetroot installed, but Core — haven't. In other hand, Core has installed yad-html package, tazweb, midori and other. Then you can return to your custom justx...
I think the best solution for you is prepare your own ISO with your flavor of choice.
Or, as option, you can boot your flavor of choice and then use one of the SliTaz tool: installer, tazlito, or just copy entire filesystem from inside booted flavor to your place. But please, understand that there are two differences: flavor you boot from Live CD and your custom extraction.
llev
offlineMember
Hi Aleksej,
I confirm the bug seen by Darjeeling. In fact he stated his tweaks just to add confusion :-D. Let me state the bug clearly: "If you boot Live rolling at the "core" stage (not rolling-core), packages yad and xorg-xsetroot are installed but do not appear in installed.info."
Details of my procedure. I use my hard disk where grub is installed to boot this.
- download rolling ISO (not rolling-core)
- mount it, copy the 4 rootfs files into /boot
- copy grub4dos.exe into /boot
- add this entry to /boot/grub/menu.lst:
title rolling via Grub4Dos
root (hd0,2)
kernel /boot/grub4dos.exe --config-file="root (hd0,2); kernel /boot/vmlinuz-3.2.71-slitaz root=/dev/null lang=fr kmap=fr-latin1; initrd /boot/rootfs4.gz /boot/rootfs3.gz /boot/rootfs2.gz /boot/rootfs1.gz"Note, this is the correct order for initrd: strangely enough, rootfs4 is the first layer (base), rootfs1 is the last (core).
My guess is there is no mean to hide/remove files of a previous layer when you add one. So the core "stage" cannot have less packages than gtkonly. (It's only my guess based on using unionfs, I don't know at all how the initramfs is actually built, it probably doesn't use unionfs.)
Aleksej
offlineCoder-hobbyist
Hi Lucas,
Thank you! It is clearly and simply written.
In fact, I thought that described behavior is related to non-official bootloader.
So the core "stage" cannot have less packages than gtkonly. (It's only my guess...)
I'll show you :)
A little background. I went through several steps to boot new SliTaz images.
At first, I unpacked the ISO, and joined four rootfs*.gz files into one by using the command cat. If I'm not mistaken, it was not yet released the slitaz-rolling-core.iso image, and the thing is, I did not know how to fit four rootfs*.gz files into my bootloader menu.list. In all my existing examples used only a single file. You know, it the wrong way. Not least because I was unpacking files in numerical order: 1, 2, 3, 4 :)
Further, when the slitaz-rolling-core.iso image appeared on a regular basis, I began to use it. At the same time my menu.list looks like this:
title SliTaz Rolling 150426
rootnoverify (hd0,6)
kernel (hd0,6)/rolling/bzImage rw root=/dev/null lang=ru_RU kmap=ru
initrd (hd0,6)/rolling/rootfs.gzHere two files used: bzImage and rootfs.gz both just extracted from the ISO.
And this year I learned that I can just run ISO without unpacking. I have a netbook, CD drive is not here. I do not buy and do not burn discs for many years. But thanks to this method, I can run the ISO in a way that was originally intended ISO creators! I see menu from ISO, it's dark image on background, I can check memory using ISO menu entry, I can select the language from the language menu, I can edit commandline... This method works very well because SliTaz ISO is so small to fit in the my not-so-big 1GB RAM. So, the lines in the menu.lst is not very complicated, and they are like as follows:
title SliTaz Rolling 151108 ISO
map --mem --heads=0 --sectors-per-track=0 (hd0,6)/rolling/slitaz-rolling.iso (hd32)
map --hook
chainloader (hd32)Using this method you'll boot the «official way», as it intended by the SliTaz creators, as it written in the flavors. And you'll see all I tell about previously.
Thanks for your attention!
Aleksej
offlineCoder-hobbyist
Hi Lucas,
It's me again. I implemented your code here: http://hg.slitaz.org/tazpkg/rev/b278bf56267b
Removing time decreased from 6 seconds to 3 seconds (on such big package as faenza-icon-theme is, and on my not-so-powerful hardware). Thank you!
llev
offlineMember
Hi Aleksej,
Thank you for the hint on booting an ISO directly with G4D! The documentation of G4D is rather clumsy, so I never tried to understand and do this (only this morning did I find the "--config-file"-and-commands trick, at first I thought I would simply "chainload" G4D with its own menu.lst).
This will save me the time for mounting and copying; more than 3 seconds ;-)
llev
offlineMember
Hi Aleksej,
I've just updated to the new tazpkg. Here's a behaviour that seems a bit strange. In tazpkg shell:
- recharge
- -cc
- up: this lists ~40 available updates; most of them are tagged "Rebuilt", e.g. avidemux; I answer "n"
- -gi avidemux: package "avidemux" is already installed, use --forced (...)
- up, answer "y": package "avidemux" already in cache, installing avidemux (...)
So: command "-gi" downloads the "rebuilt" package but will not install it. I expect it to install as command "up" does; am I wrong? If I am: why does it download something it's not going to install?
Aleksej
offlineCoder-hobbyist
Hi Lucas,
I tried to implement your requests: http://hg.slitaz.org/tazpkg/rev/8c6346ff1cef
Please, check the functions and report back.
Sorry in advance, Monday is hard day too — I'll free from work late again. On Tuesday I can devote a lot of time solving various issues.
llev
offlineMember
Thanks for using the little time you have! This can wait Tuesday, really!
tazpkg# -gi lxrandr
Le paquet « lxrandr » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
tazpkg# -gi lxrandr --forced
Le paquet « lxrandr » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.:-S
tazpkg# -g lxrandr
Connecting to mirror.slitaz.org (212.83.135.187:80)
Connecting to mirror1.slitaz.org (188.165.229.172:80)
lxrandr-0.3.0.tazpkg 100% |*******************************| 13840 0:00:00 ETA
Fait : lxrandr-0.3.0.tazpkgYipee! :-D
tazpkg# up
Rechargement du dépôt « Main »
================================================================================
Vérification... [ Fait ]
Date des index : 15/11/2015 02:01
================================================================================
Le dépôt « Main » est à jour.
Paquet Dépôt Version Status
================================================================================
java-jre Main 1.8.0_40 → 1.9.9 (Bloqués)
lxde Main 0.3.2.1 Reconstruit
lxinput Main 0.3.4 Reconstruit
lxpanel Main 0.6.2 Reconstruit
lxrandr Main 0.3.0 Reconstruit
lxsession Main 0.4.6.1 Reconstruit
lxsession-edit Main 0.2.0 Reconstruit
pcmanfm Main aa3ca1c Reconstruit (Bloqués)
scilab Main 5.5.2 Reconstruit (Bloqués)
tazpkg Main 863 → 860
================================================================================
Vous avez 7 mises à jour disponibles (3 bloqués)
693 paquets installés scannés en 1s
Voulez-vous les installer maintenant ? (o/N) o
Le paquet « lxde » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxinput » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxpanel » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxrandr » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxsession » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « lxsession-edit » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
Le paquet « tazpkg » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.So, blocked packages indeed are not updated (thanks to your new tazpkg, finally!).
"Rebuilt" packages are not either. But, first of all, what does "rebuilt" mean?
I thought it means a build dependency was changed, so the package is rebuilt even without a version change. If I'm right, then these packages should be updated, otherwise they might become inconsistent with some libs, no?
Aleksej
offlineCoder-hobbyist
Hi Lucas,
Oh, it's all night :-S Thank you for fast report!
what does "rebuilt" mean?
Our building bot, cook.slitaz.org builds a packages using receipts. Cook rebuilds package if receipt changes; it can be upgrade or downgrade, it can be any other changes in the receipt, for example in the post_install(), or it can be due to addition of "description.txt"… In addition, Pascal added special button [Recook package] to the each package log, and any package can be rebuilt in one click.
There's can be rebuild without any changes. For example, "nano" depends on "ncursesw"; if "ncursesw" is updated — it better (in minor changes) or must (in major changes) to rebuild "nano". Whatever, in any rebuilding, the md5sum of package changed (because date of compiled files is changed, and present in the package archive). TazPkg pays attention to the version changes and md5sum of the packages.
How TazPkg indicates the changes:
I tried to run tazlito gen-distro, with:
tazpkg-861 - 42M
tazpkg-862 - 38M
remove this strange 10 lines, and you'll get no missing depends.
http://hg.slitaz.org/tazpkg/rev/8c6346ff1cef#l3.7
llev
offlineMember
Hi Aleksej,
I installed tazpkg 865. I try to update a package marked as "Rebuilt":
tazpkg# -gi lxrandr
lxrandr-0.3.0.tazpkg 100% |*******************************| 13840 0:00:00 ETA
Le paquet « lxrandr » est déjà installé.
Vous pouvez utiliser l'option --forced pour forcer son installation.
tazpkg# -i lxrandr-0.3.0.tazpkg --forced
Installation du paquet « lxrandr »
================================================================================
LXDE monitor configuration tool
--------------------------------------------------------------------------------
Copie du paquet... [ Fait ]
Extraction du paquet... [ Fait ]
Mémorisation des paquets modifiés... [ Fait ]
Installation du paquet... [ Fait ]
Suppression des fichiers temporaires... [ Fait ]
Mise à jour des fichiers d'index... [ Fait ]
================================================================================
Le paquet « lxrandr » (0.3.0) est installé.
tazpkg# q
root@slitaz:~ # ls
lxrandr-0.3.0.tazpkgSo, package is downloaded although it will not be installed. It's downloaded into current WD.
Is this normal?
(If it's not normal: I'm not hurrying you! I'm just testing.)
Aleksej
offlineCoder-hobbyist
Hi Lucas,
Bug again. Seems it is bug in me :D Copy-pasting without testing, with confidence that it must to work. Hurry...
This time I tested my changes ;) and now you can test tazpkg-866: http://cook.slitaz.org/cooker.cgi?pkg=tazpkg
What's new:
tazpkg# -lb
tazpkg# -b nano
tazpkg# -gi nano
tazpkg# -gi nano --forced
tazpkg# -u nano
tazpkg# -gi nano
tazpkg# -gi nano --forcedlist-cache" to display cache content.This topic has been closed to new replies.
