Salix Forums

I'm not sure what you mean by install by hand, but spkg -d pkgname would remove the old package and then spkg -i /path/to/pkgname-newpkgver.txz would install the new one without running into that error.

Or, I'm guessing spkg -u /path/to/pkgname-newpkgver.txz would also do the trick in one step.

Oh yeah, and don't forget lilo -v after a kernel upgrade... I keep doing that.

maximus wrote:I'm not sure what you mean by install by hand, but spkg -d pkgname would remove the old package and then spkg -i /path/to/pkgname-newpkgver.txz would install the new one without running into that error.

I mean opening the packages in MC and extracting the files to their correct destinations. The reason I was asking about an override to spkg is I don't want to remove the old files - I want to keep the existing kernel in case I have problems with the new one. Haven't found a way of forcing spkg to do that yet.

Or, I'm guessing spkg -u /path/to/pkgname-newpkgver.txz would also do the trick in one step.

Still not really what I want. In the past I've often kept an existing kernel, but added a new one, then removed the old one once I was confident that the new one was working without problems. The original Slackware package tools allowed that easily enough....

Oh yeah, and don't forget lilo -v after a kernel upgrade... I keep doing that.

That's one of the reasons I don't use Lilo. I always used to forget that. I use a copy of Grub (legacy) to boot multiple Linux distibutions. Once I've got a free partition, I'll probably add a copy of the 32-bit version of Salix as well....

Paul.

OK, now I see what you're trying to do! I thought I was missing something I can't find a way to do this either. I guess you could rename the package to kernel-new or something, thereby changing the base name and avoiding the error. It's too bad spkg doesn't have the "no-upgrade" option like slapt-get:

The old slackware pkgtools are available in salix too. They are named slack-*. The slackware installpkg doesn't check if the package is already installed, so you can use that:

gapan wrote:The old slackware pkgtools are available in salix too. They are named slack-*. The slackware installpkg doesn't check if the package is already installed, so you can use that:

Code: Select all

slack-installpkg packagename

Thanks George. Didn't know the old package tools were installed as well. I'll use that - that way I can check the performance with the new drivers and the new kernel and see how that compares with the older driver and kernel.

More fun.....

Paul.