Fine tuning of usm for newcomers: your suggestions

[francois]

On another thread about solutions to missing dependencies from USM by goossbear:
http://forum.porteus.org/viewtopic.php? ... 537#p32862

It was concluded that the discussion was begining to get quite off topic. A forking of the discussion that with all its recognised advantages, it might be that usm package manager when used for porteus newcomers, though simple in its functioning, did not seem obvious as to produce the expected final result. Amongst other reasons a functional installed package working out of the bath seems to be one of these final expected result.

Whether it be in windows or in other linux distribution, the package manager is not only downloading and preparing the packages, but also installing them so that they could be ready to use. However, maybe a disadvantage of further simplicity in that line, will turn into additional computer workload.

So you are invited to provide your suggestions in terms of fine tuning of usm for newcomers.

Note that the main object of this thread is for discussing some fine tuning for now, as we really care to make sure that these fine tuning will please to both newcomers and to experienced users.

[brokenman]

I see the sense in adding MODULES=true by default (for porteus) and today I added this. I also added activate modules by default to the config file.

I also added a function to update the slackware packages so you can grab all the latest patches from slackware. I added it only to the CLI version as a testing ground as it has many caveats on a live operating system. It is currently on github.

Code: Select all

usm -u system

EDIT:
I added the following configs to the config file. Available in GUI now.

# Convert all slackware packages that are downloaded
# to porteus modules.
MODULES=true

# Activate modules after downloading them
ACTIVATEMOD=true

# Remove slackware packages after downloading
REMOVETXZ=false

[Bogomips]

Very nice. So in CLI at next update of USM?

[Ed_P]

# Activate modules after downloading them
ACTIVATEMOD=true

Will this handle when like named modules are already active? ie will it deactivate then reactivate? I'm thinking FireFox updates.

[donald]

my friend Dan (a newcomer) told me:

1.forget the CLI..all functions with GUI..else no thanks

2.build a module containing all dependencies,but only with the
needed files,not the whole (dependency) packages.

3.let me choose / browse where to save this module

4.do not auto activate,let me choose if and when.
...my friend Dan...

[Ed_P]

Code: Select all

usm -u system

???

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -u system

 Use: usm -u <distro> 
 For example: usm -u slackware

root@porteus:/home/guest# usm -v
 You are using USM version:  3.1.7

[Bogomips]

Got it from github?

[Ed_P]

Got it from github?

Actually I just did but the module is named usm-3.1.7-noarch-1.txz and i expected something like 3.1.8 or 3.1.7a to indicate it was changed. Of course I also don't know what to do with it. Do I install it or convert it to a module? I know how to do the latter but not the former.

[Bogomips]

If AF mode, just from root terminal: # installpkg usm-3.1.7-noarch-1.txz 8)

@donald
Have you told your friend Dan that there is no such thing as a free lunch?

[Ed_P]

If AF mode, just from root terminal: # installpkg usm-3.1.7-noarch-1.txz 8)

Ok Thank you Bogomips.

But how does this help me in my normal changes= mode?

[Bogomips]

But how does this help me in my normal changes= mode?

In that you can see if it is bug free, and does what it is supposed to do, before implementing into your normal changes mode, installing the way you have already done.

Would be grateful for feed back on usm -system

[Bogomips]

Enhancement Request

MODULES=true

There is one minor enhancement, while we are at it, which would be of considerable hep to me, and that is the option of being able to have the package and all it's dependent packages downloaded into a subdirectory before a module is made. At the moment, I believe, the packages are strewn all over the place in the download directory when the module option is chosen at runtime. Would be nicer to have all the TXZs for the package in the one folder.

On a another note, presumably when a module is made, it will be in the download directory, and activated there. It might be helpful here for newcomers to point out that once an application is running to their satisfaction, the module should be transferred to the modules folder or the optional folder before the next session.

[Ed_P]

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# installpkg /mnt/sda5/porteus3.0/Guest/Downloads/usm*.txz
Verifying package usm-3.1.7-noarch-1.txz.
Installing package usm-3.1.7-noarch-1.txz:
PACKAGE DESCRIPTION:
/sbin/ldconfig: /usr/lib/libv4lconvert.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib/libv4l2.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib/libv4l1.so.0 is not a symbolic link

Package usm-3.1.7-noarch-1.txz installed.

root@porteus:/home/guest# usm -v
 You are using USM version:  3.1.7

root@porteus:/home/guest# usmgui

And in the USMGUI's Settings>Edit Config File I see

Code: Select all

############ PORTEUS ONLY SETTINGS

# Convert all slackware packages that are downloaded
# to porteus modules.
MODULES=false

# Merge downloaded packages into one module bundle
MERGE=false

Am I missing something?

[brokenman]

So in CLI at next update of USM?

Correct

Will this handle when like named modules are already active?

Good question. Rare scenario because if the module is found already in the download folder it won't download it again, and therefore won't activate it. If the download is forced manually (and a like named module is already activated) then it will attempt to activate it which will infact produce a window asking if you want to deactivate. I will look at tidying that up. Thanks.

1.forget the CLI..all functions with GUI..else no thanks

Your friend Dan is welcome to forget the CLI. That's why I wrote the GUI.

2.build a module containing all dependencies,but only with the needed files,not the whole (dependency) packages.

I don't understand. He wants a module stripped of documentation and non runtime files? Is said module to be one single merged module?

3.let me choose / browse where to save this module

How can a package manager be expected to manage packages if one saves them anywhere they want? User can choose the storage location, but not where to save each individually downloaded package. Dan is free to copy the module from its storage folder to anywhere he likes. You can do this from a GUI.

4.do not auto activate,let me choose if and when.

Seems you can't satisfy 100% of the people. That was the default setting and it was questioned. No problem. Just change the settings in the (GUI) configuration and auto activate is turned off.

Am I missing something?

Perhaps you are not familiar with the concept of github. It is not sourceforge where the packages are hosted but rather a development version control system. If you're not sure then I would say just wait until the next update becomes available from within USM.

If you want to play with it then download the zip file from here: https://github.com/brokenman/usm
Then (in always fresh mode) unzip it change into the directory with the files and install it with as root: make install

[donald]

@ brokenman
Dan is a very nice person.
But when it comes to Computers,he is somewhat stubborn and don't want to learn
the "how and whys".
So yes,(imo) he wants a single (merged) module for every app,containing everything
needed to run this app.So one can hand it over to another PC, and it will still work.
(like .exe files,or when you build the module in AF mode)

I think he wants to have / build apps / module for this and that,but don't want to use
them right now...read auto activate off.

If auto activation can be turned off,and the storage location (for the merged module)
can be freely choosen,all whithin a GUI,..it should be fine..even for him. 8)