Page 11 of 25

Re: USM Unified Slackware Package Manager

Posted: 30 Mar 2014, 18:45
by Slaxmax
what is this?

Code: Select all

root@porteus:/home/guest# usm -d /var/log/packages/wine-1.7.4-i486-1sl

 Processing  wine-1.7.4-i486-1sl

####################################
cat: /tmp/usm.V0nBng/singlefile.dep: No such file or directory

####################################

Missing dependencies: 0

Re: USM Unified Slackware Package Manager

Posted: 03 Apr 2014, 03:07
by brokenman
Thanks slaxmax, I have corrected this bug when all deps are resolved and the report file does not exist.

Francois I have added the option to open the storage folder (when in GUI mode) after downloading packages.

Freestyler I will add merge of module to the module tools. This is easier since I can't tell which modules should be merged in the case that someone uses a single download folder for all packages and doesn't delete old stuff. The module tool will allow one to choose which modules they want to merge into one.

Bour I will certainly add slackware-current to USM but i wanted to test it on 14.1 first. Adding slackware-current will increase the slackware user base "10 fold" and I want it to be stable before then.

All the above changes have been added to the github only. Once i add the 'module merge' i will push another version to sourceforge as an official release. To get the updates go into the folder where you first cloned the git repository (above thread) and issue: git pull which will pull all the latest updates. Then make install to install the new files from the source code. If you are asked about overwriting a man file just say yes. This is a slackware file no harm done overwriting in in Porteus.

Thanks very much for road testing this guys. You are all great.

Re: USM Unified Slackware Package Manager

Posted: 03 Apr 2014, 03:59
by freestyler
love your work brokenman

Re: USM Unified Slackware Package Manager

Posted: 03 Apr 2014, 14:01
by fanthom
certainly add slackware-current to USM but i wanted to test it on 14.1
sooner or later you'll get breakage (depends how far Pat goes with libs bumping) . bad idea to include -current.

Re: USM Unified Slackware Package Manager

Posted: 03 Apr 2014, 16:50
by bour59
Hi!
I thought
/slackware gave tested packages (base)
/currentpatches gave packages to be tested (more accurate)
/current gave packages tested to suit the version of slackware after tested in patches
pls add a warning in packages (patches and current) but add
thanks

Re: USM Unified Slackware Package Manager

Posted: 03 Apr 2014, 17:13
by fanthom
slackware patches is ok as is compiled on stable release.
-current is a 'pre' new release so things must break at some stage.

Re: USM Unified Slackware Package Manager

Posted: 03 Apr 2014, 18:20
by bour59
ok
I made my proposal based on bind package
which was 9.9.3 in slackware base
then 9.9.4 in testing (runs also)
and is now in current at 9.9.4 (runs always)
sure I can't create a general rule from this tests!
thanks to let me very prudent (as always)
but, let propose current with WARNINGS

Re: USM Unified Slackware Package Manager

Posted: 04 Apr 2014, 00:51
by brokenman
As the application is both for Porteus users and slackware users I intended to allow slackware-current for slackware users. Porteus users will need to stick to Porteus/Slackware version. Some slackware users run only slackware-current and want only packages from slackware-current. When changing versions the database would overwrite the existing one. So, users can choose one or the other but not mix both.

Re: USM Unified Slackware Package Manager

Posted: 04 Apr 2014, 02:17
by francois
Repeating some previous comments. Keep that really good work. usm is a big improvement over ppm.

Thanks.

Re: USM Unified Slackware Package Manager

Posted: 04 Apr 2014, 03:11
by francois
Hello Jay:
Francois I have added the option to open the storage folder (when in GUI mode) after downloading packages.

Trying to update usm, I get:

Code: Select all

You have the current usm version
Trying to download most up to date files thru git, I get:

Code: Select all

root@porteus:~# git clone https://github.com/brokenman/usm.git
fatal: destination path 'usm' already exists and is not an empty directory.
root@porteus:~# 
What did I caught wrong? (cognitive functioning after a certain age seems to become random) :%)

Thanks.

Re: USM Unified Slackware Package Manager

Posted: 04 Apr 2014, 03:41
by brokenman
Once you have cloned the tree you just need to issue: git pull to get the latest files.

For example:

Code: Select all

cd /home/guest
git clone https://github.com/brokenman/usm.git
Two days later

Code: Select all

cd /home/guest
git pull
BTW I just added the option to merge multiple packages into one module (only for CLI so far). If multiple packages are sensed then it will ask if you want to merge them or create a separate folder for them. I will add the same function for GUI soon. These options are only available on Porteus installs, not slackware.

PS: cognitive functioning after a certain age does indeed seem .... I think I will get an ice cream.

Re: USM Unified Slackware Package Manager

Posted: 07 Apr 2014, 16:08
by brokenman
Updated to 3.1.1

Please run: usm -u usm to get the latest version.

+-------------------------
Fri Apr 07 13:21:10 UTC 2014
usm-3.1.1-noarch-1.txz: updated
Added GUI merge packages to module for Porteus (freestyler)

+-------------------------
Fri Apr 04 00:27:17 UTC 2014
Added CLI merge packages to module for Porteus (freestyler)

+-------------------------
Thu Apr 03 10:38:27 UTC 2014
Checkbox for convert to module now remembers state

+-------------------------
Wed Apr 02 23:22:09 UTC 2014
Fixed bug in system deps when all deps are resolved - Thanks slaxmax
Added option to open folder after package download - Thanks Francois
Added nodeps argument in CLI mode

+-------------------------
Tue Mar 18 22:09:14 UTC 2014
Added support for proxies
Added support resolve deps for single uninstalled package

Re: USM Unified Slackware Package Manager

Posted: 08 Apr 2014, 19:06
by francois
Thanks a lot for all these additional features.

May you add a clean slackware packages after modules building (keep only the modules) setting? :)

Re: USM Unified Slackware Package Manager

Posted: 08 Apr 2014, 23:12
by brokenman
Thanks. Will add it to the next version.

Re: USM Unified Slackware Package Manager

Posted: 10 Apr 2014, 13:07
by brokenman
@bour59
I apologize. I now see what you were saying about the slackwarepatches database not being updated. You are correct. I will fix this shortly.