Fine tuning of usm for newcomers: your suggestions

[Bogomips]

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)

IMHO that was the 'bundles' project, or am I missing something here? On another note, has your friend Dan got deep pockets?

[Ed_P]

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,

The situation I am referring to is where the new module would be in the download folder but the active version would be in the porteus/modules folder. Not as rare as you may think imo.

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

Oh! So I would have to compile it!! Ok, I'm not sure I'm to that level yet. Thanks.

[Bogomips]

At end of dependency processing unresolved dependencies now flagged, together with colorised warning! Thanks.

[donald]

@ Bogomips
The "bundles project"...is it alive?...where are these bundles?
hmmm..
I have been told that it is better not to use/install software
not coming from the official Repositories.
as a reminder:
If you install other peoples software,you shortly give them root privileges on the computer.
--security risk--

btw
--> has your friend Dan got deep pockets? <--
I read the text, but I do not understand the meaning.
is it a saying?..

[brokenman]

The situation I am referring to is where the new module would be in the download folder but the active version would be in the porteus/modules folder. Not as rare as you may think imo.

If there is an 'active' version in the porteus modules folder then it would have been mounted at boot time. Therefore the libraries would be processed by USM and the same module would not be downloaded again, hence never making it into the download folder.

[Ed_P]

If there is an 'active' version in the porteus modules folder then it would have been mounted at boot time. Therefore the libraries would be processed by USM and the same module would not be downloaded again, hence never making it into the download folder.

I'm confused. I'm not seeing it that way.

Code: Select all

guest@porteus:~$ cat /mnt/live/memory/images/*firefox*
cat: /mnt/live/memory/images/mozilla-firefox-31.5.0esr-x86_64-1_slack14.1.xzm: Is a directory


>>> firefox is mounted

 
guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -g mozilla-firefox

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) mozilla-firefox-24.1.0esr-x86_64-1.txz
2) mozilla-firefox-31.5.0esr-x86_64-1_slack14.1.txz
3) mozilla-firefox-31.6.0esr-x86_64-1gv.txz
#? 3


>>> usm finds multiple firefox modules including the same one mounted



Processing:   mozilla-firefox-31.6.0esr-x86_64-1gv.txz 
Ignored libraries: 

Libraries required:  39
Libraries found in system: 39
Libraries to resolve: 0



 The following packages are required. 
mozilla-firefox-31.6.0esr-x86_64-1gv.txz [33192K] [upgrade]

Total size: 33 MB
 Would you like to install the package/s? (custom paths are supported) [y/n]


>>>> usm is going to download the new version of firefox

Will usm deactivate the mounted version prior to usm activating the new download?

[francois]

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

Thanks for these swift modifications. I have the impression that newcomers, especially those less familiar with Linux, will this way be introduced more easily to the porteus way.

[francois]

@ed:
git is really not complicated, see:
viewtopic.php?f=75&t=3040&start=165

1.0 install the git package with USM and get the devel.xzm package for current porteus. There are no other dependencies. 8)
2.0

Code: Select all

root@porteus:~# git clone https://github.com/brokenman/usm.git
root@porteus:~#

[brokenman]

I will just add that after you clone the git repository you change into the directory and run make.

Code: Select all

cd usm
make STRIP_COMMENTS=false install

If you want to create a module.

Code: Select all

mkdir /tmp/mynewusm
make DESTDIR=/tmp/mynewusm install
dir2xzm /tmp/mynewusm /tmp/mynewusm.xzm

This will overwrite your current USM if you are saving changes.

[brokenman]

Will usm deactivate the mounted version prior to usm activating the new download?

Ok I see the confusion. I am talking about modules with the same name. No, it won't deactivate a module with a different name. It will simply activate the new module over the old one.

[Bogomips]

usm -g <package> depth=n
Would it present much difficulty to have the normal closing sequence

Code: Select all

 Multiple packages were detected.
 Would you like to merge the packages into one module? [y/n]
 Would you like to create a subfolder for the files? [y/n]
 Would you like to install the package/s? (custom paths are supported) [y/n]

 Press [r] to remove packages, [q] to quit, or enter to start downloading.

when depth n is reached?

At the moment it is something like this:

Code: Select all

root@porteus:/home/guest# usm -g gimp depth=3

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) gimp-2.8.6-i486-1.txz
#? 1

Processing:   gimp-2.8.6-i486-1.txz 
Ignored libraries: 

Libraries required:  95
Libraries found in system: 80
Libraries to resolve: 15
...
Processing:   aalib-1.4rc5-i486-5.txz 
Ignored libraries: 

Libraries required:  10
Libraries found in system: 9
Libraries to resolve: 1

Processing library: libaa.so.1
...
Processing:   babl-0.1.10-i486-1.txz 
Ignored libraries: 

Libraries required:  3
Libraries found in system: 2
Libraries to resolve: 1

Processing library: libbabl-0.1.so.0
...
Processing:   gegl-0.2.0-i486-2.txz 
Ignored libraries: 

Libraries required:  66
Libraries found in system: 58
Libraries to resolve: 8
...
Processing:   ghostscript-9.07-i486-2.txz 
Ignored libraries: 

Libraries required:  72
Libraries found in system: 69
Libraries to resolve: 3

Processing library: libcups.so.2

 More than one package contains:  libcups.so.2
cups-1.5.4-i486-3.txz        1856K  slackware
aaa_elflibs-14.1-i486-3.txz  4708K  slackware

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) cups-1.5.4-i486-3.txz
2) aaa_elflibs-14.1-i486-3.txz
#? 2
Processing library: libcupsimage.so.2
Processing library: libgs.so.9

Depth 5 of resolution reached. Exiting.

The option of downloading packages found up to this point could have been quite beneficial in certain instances, which had previously arisen.

[brokenman]

I don't think it would be too difficult. Just a matter of checking for 'n' and then adding a return command. I will check it out. Thanks for the suggestion.

[francois]

Your closing sequence makes a lot more sense.

Interesting suggestion bogomips, so depth = number of maximum packages to look for as dependencies?

Note: this post was corrected hoping to make more sense.

[Bogomips]

Interesting suggestion bogomips, so depth would be the number of maximum packages to look for as dependencies? And your closing sequence makes a lot more sense.

If I understand you correctly, then I think I would be right in asserting that: depth!=max number of packages, if that was your presumption.

[francois]

I hope that my wording express my thoughts better in the above post.