[SOLVED] multi installing .tgz files

BW-userx · 12-12-2016, 01:07 PM

I got a lot of .tgz files, I've saved from installing them into Slack. On a new install of slack, after post installation has been completed.

if is possible to install everything I have using something like this?

Code:

installpkg /run/media/userx/WD3TB/Slackware-tgz-files/*

seeing how everything within that directory is *.tgz files. Will slack be able to handle that, one file after the other until they are all installed?

Gerard Lally · 12-12-2016, 01:14 PM

Quote:

Originally Posted by BW-userx

I got a lot of .tgz files, I've saved from installing them into Slack. On a new install of slack, after post installation has been completed.

if is possible to install everything I have using something like this?

Code:

installpkg /run/media/userx/WD3TB/Slackware-tgz-files/*

seeing how everything within that directory is *.tgz files. Will slack be able to handle that, one file after the other until they are all installed?

Here's one way of doing it:

Code:

cd /run/media/userx/WD3TB/Slackware-tgz-files/
for p in *.t?z
do
installpkg $p
done

BW-userx · 12-12-2016, 01:18 PM

Quote:

Originally Posted by gezley

Here's one way of doing it:

Code:

cd /run/media/userx/WD3TB/Slackware-tgz-files/
for p in *.t?z
do
installpkg $p
done

this is going to be interesting. Thanks I see the logic and am going to give that a whirl.

bassmadrigal · 12-12-2016, 01:32 PM

{install,upgrade,remove}pkg all work fine with wildcards (unless with that wildcard expansion you manage to surpass the limits of the shell, which on a 14.2 64bit install is over 2 million characters).

I've run commands such as upgradepkg --reinstall --install-new */*/*.t?z without any issues. The question mark in the extension allows for both .tgz and .txz packages.

I don't see any immediate reason to use a for loop unless you're looking at limiting what you're trying to install.

BW-userx · 12-12-2016, 01:37 PM

Quote:

Originally Posted by bassmadrigal

{install,upgrade,remove}pkg all work fine with wildcards (unless with that wildcard expansion you manage to surpass the limits of the shell, which on a 14.2 64bit install is over 2 million characters).

I've run commands such as upgradepkg --reinstall --install-new */*/*.t?z without any issues. The question mark in the extension allows for both .tgz and .txz packages.

I don't see any immediate reason to use a for loop unless you're looking at limiting what you're trying to install.

no not really tying to limit it at all. file manager states 40 files. so that is like way within 2 million character limits.

so what I wrote too would work? I am making my USB Stick right now. as soon as that is done I will be installing slack.

bassmadrigal · 12-12-2016, 01:49 PM

Yes, you can either cd into the directory and just type installpkg * or you can run it from wherever you're at and provide the full path installpkg /run/media/userx/WD3TB/Slackware-tgz-files/* like in your first example.

However, personally, I would always use a *.tgz, *.txz, or *.t?z just as a general guideline whenever I'm working with a specific type of files. I'm pretty sure pkgtools will ignore non-package files, but it's still a good practice to get into (especially with deleting things).

So, personally, I would do:

Code:

installpkg /run/media/userx/WD3TB/Slackware-tgz-files/*.tgz

RandomTroll · 12-12-2016, 02:24 PM

I started Slacking 20 years ago and do my own updates. I've never had a problem with

Code:

 installpkg *.t?z

.

All of my Slackware packages are .txz now; are they .tgz somewhere?

BW-userx · 12-12-2016, 02:28 PM

Quote:

Originally Posted by RandomTroll

I started Slacking 20 years ago and do my own updates. I've never had a problem with

Code:

 installpkg *.t?z

.

All of my Slackware packages are .txz now; are they .tgz somewhere?

yes everything I built off of slackBuilds, I kept somewhere safe. for reinstall if I needed to so I would not have to do everything all over again.

so you must have been in the same directory when you ran that command?

BW-userx · 12-12-2016, 02:30 PM

Quote:

Originally Posted by bassmadrigal

Yes, you can either cd into the directory and just type installpkg * or you can run it from wherever you're at and provide the full path installpkg /run/media/userx/WD3TB/Slackware-tgz-files/* like in your first example.

However, personally, I would always use a *.tgz, *.txz, or *.t?z just as a general guideline whenever I'm working with a specific type of files. I'm pretty sure pkgtools will ignore non-package files, but it's still a good practice to get into (especially with deleting things).

So, personally, I would do:

Code:

installpkg /run/media/userx/WD3TB/Slackware-tgz-files/*.tgz

exactly, but I wrote it like that only because everything within that dir is tgz only. so it saves my fingers .

lol