user feedback
 

@phenixia2003: Thanks for answering my questions.

Regarding improvement of "install-new" function to support 3rd-party repositories, I would definitely prefer option (2): i.e. make it optional so user has to manually select in config file which repository(ies) to be added to appear in "install-new".

To stay consistent with what slackpkg does with the official Slackware repository, I would vote for option a). List of new packages in a 3rd-party repository would only be listed with command "slackpkg install-new" ,of course the repository must first have been "selected" for "install-new". I'm not aware of another way to list the new Slackware packages using slackpkg.

Notice that the official install-new shown all new packages from the previous stable release to the latest new package, and not from the latest slackpkg update command or the latest install-new command unless you install or blacklist the new packages.

If you do that for a thirdy party repository started empty, slackpkg install-new will show the same output of slackpkg install repository that is not useful becouse I dont think that a user want install an entire repository that contains heterogeneous or conflicting packages. A similar install-new may be useful for repositories that suppose you want fully install as multilib, ktown, gsb... that contains multiple package for a single purpose; if you run slackpkg upgrade ktown may be needed to run slackpkg install ktown. If you run slackpkg upgrade alienbob I don't think that you need to run slackpkg install alienbob.

Again, be very careful not to mess with the default behaviour of slackpkg.

Eric

Hello,

Just an idea: For a given repository, all the changes collected when running "slackpkg update" could be merged, version by version :

What do you mean by "third party repository started empty ?" A repository with 0 packages, then you add 10, etc

For a given repository R, "slackpkg install R" will only show the uninstalled packages, and, slackpkg install-new, will only show the packages identified as new.

For a repository R, when you run "slackpkg update", a snapshot of available packages is taken, then the data are fetched from the repository, and a new snapshot is taken. When these snapshots are different, the changes are collected :



Important:
Keep in mind that implementation of "install-new" I sent last day is incomplete and must be (really) considered as a work in progress. It needs more attention, because it does not take care of defined priorities, nor the packages that could have been installed manually or by any other ways.

Cheers.

--
SeB

For info, I will continue developing next monday. This weekend I've not my pc, and I may not read the forum.

regarding the install-new functionality for now I would wait.

In the development tree I added other features.

All feature from the stable and now:

- Added ALLOW32BIT flag to allow to install 32bit packages on a 64bit system
- Added an install log in /var/lib/slackpkg/install.log; launching "/usr/libexec/slackpkg/makeinstlog.sh -t" TRY to detect the repository from which the packages was installed
- Added WGETOPTS
- Added the greylist

Are all embrional code

well... the install.log function is bugged :) when you install multiple packages!
due a VERY BAD cut/paste ;)

Hello,

I totally agree.


--
SeB

Hello,

About this, It would be great to automatically put 32-bit packages on greylist (I didn't check if this can be done at runtime) when user runs "slackpkg upgrade" / "slackpkg upgrade-all". With that, the user would have to explicitly select the 32-bit packages he wants to upgrade, and this will prevent him to mistakenly upgrade some of installed packages with 32-bit version.


--
SeB

Yes it's possible.
slackpkg+-20131119.3-noarch-1mt.txz do that.

Hello,

Good job :cool:

Cheers.

--
SeB

Hello,

I wrote a small patch for slackpkg+ (Attachment 15163) which solves this small bug, and adds a small improvement so that the command slackpkg check-updates reports the repositories which have been changed since the last update.

Here is an example of the new output of check-updates :
The name of each updated repository is saved in ~/.slackpkg/updated-repos.txt. When there's no update, this file is empty.

With that, you can create a crontab entry to be notified through a tooltip inside your preferred DE when updates are available. For instance, to check updates every 2 hours at the top of the hour :

Note: the crontab entry above is for non-root users only: notify-send does not work when run as root. To workaround this, users who really want to run notify-send as root, can use this wrapper.

Examples:

1. Kde
Attachment 15161

2. Xfce
Attachment 15162

Greetings.

--
SeB

Good feature.

Currently I don't have my GPG-KEY ;), so I can't update the repository metadata (so it is not available with slackpkg upgrade slackpkg+), but I uploaded the new package on sourceforge.

Thank you phenixia2003 for this latest patch.

The DE notification is working fine except for the time details in the crontab entry.

runs the code every minute (i.e notification every minute).

I'm no crontab specialist, but to make it run once an hour, I would rather use something like that:

Every hour at 0 minute (ex: 21h00, 22h00....)
Every 59 minutes (I don't know if 60 works here)
For now, I've settled for every 55mn:
I'm currently testing, so I will wait 55mn to confirm that this entry works. But at least, for now, I don't have the notification every minute :)

Now that you have a notification you just need to add a quick start button that runs "slackpkg" update and upgrade, both graphically and automatically. Then you will have removed one of the "major fictions" of Slackware. That being, that it doesn't have a package manager.

samac