Salix OS

No idea what that dir is for though.

I still don't think that we should keep the original tools in the package. I don't think anyone is ever going to use them, nobody will really know they are there unless they look in the package contents. I guess that if someone wants to use the original pkgtools, he will just get the package from slackware. But since you insist on keeping them, no problem.

Found a problem. Installing txz packages the entry in /var/log/packages has a txz extension.

gapan wrote:Found a problem. Installing txz packages the entry in /var/log/packages has a txz extension.

I've sent a bug report to the developer.

gapan wrote:

Code: Select all

Directory var/log/setup/tmp/ has no read permssions

No idea what that dir is for though.

Taken from the original SlackBuild:
chmod 700 $startdir/pkg/var/log/setup/tmp

No idea what's this for.

gapan wrote:I still don't think that we should keep the original tools in the package. I don't think anyone is ever going to use them, nobody will really know they are there unless they look in the package contents. I guess that if someone wants to use the original pkgtools, he will just get the package from slackware. But since you insist on keeping them, no problem.

I don't insist on it, but I think it's no problem to have them. The spkg preload thing is untested and it can't be bad to have a working fallback solution.

gapan wrote:Found a problem. Installing txz packages the entry in /var/log/packages has a txz extension.

Patched version uploaded. But you have to use slack-upgradepkg to reinstall packages that have the txz extension in /var/log/packages.

I think spkg-pkgtools should be tgz instead of txz.

thenktor wrote:
gapan wrote:
Code:
Directory var/log/setup/tmp/ has no read permssions

No idea what that dir is for though.

Taken from the original SlackBuild:
chmod 700 $startdir/pkg/var/log/setup/tmp

No idea what's this for.

Afaik it's used during install time. The installer stores there all?/?some temporary files and sg2conf puts its there too.

thenktor, you were absolutely right about keeping a copy of the original pkgtools inside the package. Just found a case where spkg won't work.
If two different versions of a package are installed, spkg can't remove either one of them, even if specifying the full path in /var/log/packages, slack-removepkg will remove the 1st one and then the 2nd one if it is run again, and whichever you choose if you specify the full path!

OK. Maybe this could be reported back to spkg developer, or maybe another patch ?

JRD wrote:OK. Maybe this could be reported back to spkg developer, or maybe another patch ?

I've sent the bug report.