|
Yeah it's ARM, is there a specific forum for ARM installs? I assumed this would be OK here with this being the Installation forum.
I created some packages containing the kernel and firmware for raspberry pis.
I dropped them into the slackware Y directory and edited the tagfile in that directory.
I ran the setup script, and selected a full install, which installed every .tgz file in that directory whether it was listed in the tagfile or not, and irrelevant of any SKP tagfile entry for that package.
I ran it again using the terse option and it did the same thing.
I went back to the slackware 14.0 installer, it behaved in exactly the same way.
You can see the contents of my y/tagfile in my OP, and the results from the terse install performed by the slackware arm 14.2 installer. I've now confirmed the 14.0 installer behaves in exactly the same way when presented with the same directory structure.
There was also the odd case of the xf86-input-aiptek package, which is in the X directory tree.
Presumably added during some kind of update, but not added into the tagfile.
I don't install x at all. So all entries in the tagfile are set to SKP, and the installer skips every package, but it installed the one package which wasn't listed in the tagfile, but which was in the x directory. The only modification I made to that directory was to change all tags in the tagfile to SKP.
The oddest thing is the installer doesn't install bsd-games (tagged as SKP) but installs all other packages tagged as SKP, and even packages that are in the directory but not listed in the tagfile. That's the bit I can't get my head around, it reads SKP against bsd-games and skips it, but then doesn't skip other package listings from the same tagfile also marked SKP.
I haven't tried it on the x86 trees I run yet, so I've no idea if it behaves the same way there. I will get to that, after I've tried working around this, and tidying some stuff up.
|
