ncurses, tango-icon-theme, and texlive, and manual installation of slackware
by slac-in-the-box from LinuxQuestions.org on (#52VVS)
Howdy slackers.
Sometimes I still manually install slackware. What I mean by manual install, is creating a directory, and using the --root flag to installpkg to install the slackware packages to said directory. Here's an example, executed from within the top level of the slackware source tree, that contains the directories a, ap, d, e, and so on:
Code:mkdir /target
installpkg --root /target a/*.t?z ap/*.t?z d/*.t?z e/*.t?z kde/*.t?z l/*.t?z n/*.t?z t/*.t?z tcl/*.t?z x/*.t?z xap/*.t?z xfce/*.t?z y/*.t?zOn x64 as well as arm64, (only architectures I've been using of late), when I do this, everything proceeds the way I expect, with the package descriptions flashing by, until it gets to ncurses in the "n" set, which it installs; but every subsequent package in the "n" set and the rest of the command fail, with "file not found" errors.
The same thing occurs with tango-icon-theme, and texlive.
I've never really asked about it, because it's been easy enough to just install the "a" set, and then manually install the three troublesome packages and move them out of their set directories. The batch install then succeeds with the remaining sets of packages.
Wondering why these packages are anomalies in the manual install process, is like an itch I haven't been able to reach for a long time.
Any ideas?
Sometimes I still manually install slackware. What I mean by manual install, is creating a directory, and using the --root flag to installpkg to install the slackware packages to said directory. Here's an example, executed from within the top level of the slackware source tree, that contains the directories a, ap, d, e, and so on:
Code:mkdir /target
installpkg --root /target a/*.t?z ap/*.t?z d/*.t?z e/*.t?z kde/*.t?z l/*.t?z n/*.t?z t/*.t?z tcl/*.t?z x/*.t?z xap/*.t?z xfce/*.t?z y/*.t?zOn x64 as well as arm64, (only architectures I've been using of late), when I do this, everything proceeds the way I expect, with the package descriptions flashing by, until it gets to ncurses in the "n" set, which it installs; but every subsequent package in the "n" set and the rest of the command fail, with "file not found" errors.
The same thing occurs with tango-icon-theme, and texlive.
I've never really asked about it, because it's been easy enough to just install the "a" set, and then manually install the three troublesome packages and move them out of their set directories. The batch install then succeeds with the remaining sets of packages.
Wondering why these packages are anomalies in the manual install process, is like an itch I haven't been able to reach for a long time.
Any ideas?