Page 21 of 25
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 02:27
by brokenman
I have the impression that this would exactly do the job.
@Francois
Added option in GUI to install packages instead of opening target folder.
Found "Choose an number to confirm." somewhat confusing. Looked like it was going to enter a download phase.
@ Bogomips
Sorry, I disagree. If you are requesting info (-i) why would one think it is entering a download phase? The label here is a generic CLI menu so it is the same label for whatever calls it. Changing it for one (-i) could make it confusing for another (-g) so I will stick with the generic label for now.
It might be wise to delete the dependency files after the module is created.
@Ed_P
This is not viable in the case where one wants to manage packages. Deleting the slackware package means it will need to be redownloaded next time it is required as a dependency. I think leaving deletion of files to the user is the best idea.
Thanks for the suggestions.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 04:03
by Ed_P
brokenman wrote:It might be wise to delete the dependency files after the module is created.
@Ed_P
This is not viable in the case where one wants to manage packages. Deleting the slackware package means it will need to be redownloaded next time it is required as a dependency.
I don't understand. If a package is added to a module why would it need to be added to a different module? If it's active in one isn't it available to other modules? And once the module is created when the system is rebooted these /tmp/usm packages are all deleted.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 10:13
by brokenman
If a package is added to a module why would it need to be added to a different module?
Yes, but this assumes one is moving the package to the modules folder and actually WANTS them activated at every boot. Some people may prefer to activate on demand and in this case may even prefer bundles.
And once the module is created when the system is rebooted these /tmp/usm packages are all deleted.
Assuming one does not use changes.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 14:11
by Ed_P
brokenman wrote:And once the module is created when the system is rebooted these /tmp/usm packages are all deleted.
Assuming one does not use changes.
changes=EXIT does not save the /tmp/ directory.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 14:32
by fanthom
/tmp folder should be used for storing of temporary files.
if USM files supposed to be persistent then i would consider placing them in /usr/share/usm or even /opt/usm.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 15:46
by Ed_P
Ideally, if a user selects the USM option to have the downloaded packages made into a module the module could be placed in the user's extramod directory, either by default or as an option. That would eliminate the user having to find it amongst all the dependencies.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 16:01
by brokenman
the module could be placed in the user's extramod directory, either by default or as an option.
USM has no way of knowing the location of your extramods directory. It could be anywhere. User can just as easily use extramod= to point to their USM storage.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 16:10
by Ed_P
gee, the "cat /proc/cmdline" command in RazorQT shows me the directory where my extramods option is pointing to. Don't know if would work in other DEs.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 17:22
by brokenman
gee, the "cat /proc/cmdline" command in RazorQT shows me the directory where my extramods option is pointing to.
That's nice for you. You added the cheat code. Mine doesn't show me any extramods folder. I have to think 'in general' where 95% of users don't use this cheat, and the folder where they like to store extra stuff may be unknown. One folder is known ... $STORAGE. It can act like an extramod folder and you can more easily point your cheat code there than I can add code for all situations. Thanks.
Re: USM Unified Slackware Package Manager
Posted: 02 Oct 2014, 21:49
by Ed_P
brokenman wrote:I have to think 'in general' where 95% of users don't use this cheat, and the folder where they like to store extra stuff may be unknown.
You're probably right. Better to use
fanthom's suggestion and put the downloaded packages and modules in /usr/share/usm or even /opt/usm. Then a user's storage options doesn't matter and coding should be simpler.
Re: USM Unified Slackware Package Manager
Posted: 03 Oct 2014, 02:22
by brokenman
What about $HOME/usm ??
Re: USM Unified Slackware Package Manager
Posted: 05 Oct 2014, 05:37
by Slaxmax
database was updated, but yet show message to update.
Code: Select all
root@porteus:/home/guest# usm -v
You are using USM version: 3.1.6
root@porteus:/home/guest# usm -u all
alien was updated 776 seconds ago. Skipping.
salix was updated 48 seconds ago. Skipping.
slacky was updated 742 seconds ago. Skipping.
ponce was updated 723 seconds ago. Skipping.
slackware was updated 314 seconds ago. Skipping.
slackwarepatches was updated 234 seconds ago. Skipping.
sbo was updated 54 seconds ago. Skipping.
extra-deps.txt was updated 48 seconds ago. Skipping.
ignore-deps.txt was updated 48 seconds ago. Skipping.
You can change the time limit for skipping in: /etc/usm/usm.conf
The default is 3 hours
root@porteus:/home/guest# usm -g gnutls
The following items were found.
Choose an number to confirm.
ctrl+c to quit
1) gnutls-3.1.16-i486-1.txz
2) gnutls-3.1.25-i486-1_slack14.1.txz
#? 2
Processing: gnutls-3.1.25-i486-1_slack14.1.txz
Ignored libraries:
Libraries required: 15
Libraries found in system: 14
Libraries to resolve: 1
Processing library: libgnutls.so.28
The following packages are required.
gnutls-3.1.25-i486-1_slack14.1.txz [1984K]
Total size: 1 MB
Press [r] to remove packages, [q] to quit, or enter to start downloading.
Updates are available.
Program update: not required
Database update: available
Please run: usm -u all and/or usm -u usm
This message can be disabled in /etc/usm/usm.conf
###############################
gnutls-3.1.25-i486-1_slack14.1.txz already exists
root@porteus:/home/guest#
and gnutls downloaded 0B
Re: USM Unified Slackware Package Manager
Posted: 06 Oct 2014, 18:33
by Slaxmax
@Brokenman
An interesting option would automatically choose the dependencies without warnings.
For example always choose the smaller package.
And in the end show the option to choose the package you want to download, or remove some.
thx
Re: USM Unified Slackware Package Manager
Posted: 18 Oct 2014, 01:25
by brokenman
Thanks Slaxmax. I will take a look at this option. Progress was frozen until the release of Porteus v3.1rc1 which will be available very soon (probably tomorrow).
I have just now updated USM to v3.1.7 but you may want to wait for the new Porteus version instead.
Re: USM Unified Slackware Package Manager
Posted: 20 Oct 2014, 23:52
by brokenman
Updated USM database.