SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi.
Adding progress percentage in slackpkg is simpler than slackpkg+ and more complete
This is for Release 2.84.0_beta6 (commit d3632208a5b190f1c68aac3c6a36b9a7bdf6dffc)
1) add function progress that print the percentage
2) in every install-new, upgrade-all etc you have to calculate packages before than start analyze them, then count, then use them
3) a slower operation is preparing the dialog box, so you can add a progress here
4) during install/upgrade you can print the progress
Suggests:
on /etc/slackpkg/mirrors leave https://mirrors.slackware.com/slackw...are64-current/ uncommented by default since it is the official mirror and autoswitching to localized mirror, so slackpkg is ready to use.
Hello.
It's time that I fix slackpkg+ for using $ROOT since starting slackpkg 2.82.3 changed how it works applying it to $WORKDIR, $TEMP, and $TMPDIR instances.
But this commit confuse me:
Code:
commit a9c7e7d4c7d40b36965bcf8a45419c2de6d04954
Author: Robby Workman <rworkman@slackware.com>
Date: Mon Jan 14 23:17:13 2019 -0600
Fixup blacklist checking and appending when using alt $ROOT
Thanks to dive for the report.
From code, slackpkg does not apply $ROOT to $CONF/slackpkg.conf and $CONF/mirrors, but partially apply it to $CONF/blacklist
it's correct that:
1) $CONF does not honor $ROOT ?
2) $CONF/blacklist does honor $ROOT ?
This is admittedly confusing, and frankly, I'm not sure I understand why we did it that way. I can at least rationalize some of it though...
Assuming we are installing to an alternate $ROOT, we want to check the altroot's blacklist (hence line 595).
It looks like 647 and 1235 were overlooked, so I'm going to fix those up.
Line 1283 is adding things to blacklist and thus it is reasonable to add them to the altroot's blacklist if $ROOT is defined.
I'll also fix up line 469 in the slackpkg script itself.
This ROOT support is fragile. :/ I wouldn't have undertaken it had it been my call, but it was already (partially) supported (but broken) for some use cases, so fixes were committed, which led to more fixes, and so on until here we are... I just hope nothing breaks as result of the changes I'm about to commit... :/
This is admittedly confusing, and frankly, I'm not sure I understand why we did it that way. I can at least rationalize some of it though...
Assuming we are installing to an alternate $ROOT, we want to check the altroot's blacklist (hence line 595).
It looks like 647 and 1235 were overlooked, so I'm going to fix those up.
Line 1283 is adding things to blacklist and thus it is reasonable to add them to the altroot's blacklist if $ROOT is defined.
I'll also fix up line 469 in the slackpkg script itself.
This ROOT support is fragile. :/ I wouldn't have undertaken it had it been my call, but it was already (partially) supported (but broken) for some use cases, so fixes were committed, which led to more fixes, and so on until here we are... I just hope nothing breaks as result of the changes I'm about to commit... :/
it seems, unfortunately, that the new modifications introduced between beta6 and beta7 actually break the lxc template (beta6 was working fine): I was testing a new version of the template (that I revised mostly last summer) with a newer version of lxc that should work fine on current
seems that *forcing* $CONF under $ROOT is what break things here: $CONF in the template is used to have a temporary location, outside of the container, in which to store the template, a blacklist and a mirror configuration for the container creation.
IMHO is not essential to enforce $CONF under $ROOT as it can specified manually at the same location (CONF=/chroot/etc/slackpkg) as needed with losing no functionality.
it seems, unfortunately, that the new modifications introduced between beta6 and beta7 actually break the lxc template (beta6 was working fine): I was testing a new version of the template (that I revised mostly last summer) with a newer version of lxc that should work fine on current
seems that *forcing* $CONF under $ROOT is what break things here: $CONF in the template is used to have a temporary location, outside of the container, in which to store the template, a blacklist and a mirror configuration for the container creation.
IMHO is not essential to enforce $CONF under $ROOT as it can specified manually at the same location (CONF=/chroot/etc/slackpkg) as needed with losing no functionality.
It's reverted. I don't like the inconsistency with ROOT definitions but I'm not going to break our upstream either :-)
Unless something major comes along and/or some very trivial things occur, consider 2.84.0_beta8 to be what will hopefully become 2.84.0.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.