Hi!

For a long time I'm using for upgrade of packages I compiled.
For others (system, alien, ktown..) I use slackpkg+.

Recently I was surprised when I found:
/var/lib/pkgtools//packages/zoneminder-1.34.14-x86_64-GIT-20200520_ZD
/var/lib/pkgtools//packages/zoneminder-1.34.15-x86_64-GIT-20200522_ZD
/var/lib/pkgtools//packages/zoneminder-1.35.4-x86_64-GIT-20200604_ZD
/var/lib/pkgtools//packages/zoneminder-1.35.5-x86_64-GIT-20200730_ZD
on my test machine.

What could be the reason for the above? Does upgradepkg consider a minor package version change as a new package and so install a new version as a totally different program?
So far I did not notice such behavior of upgradepkg.
Using oldpkg%newpkg notation would be unnecessary complication.

the name of a Slackware package is composed of different alphanumeric variables, separated by dashes ("-"), like $PKGNAM-$VERSION-$ARCH-$BUILD$TAG
what happens to you probably does because the $BUILD$TAG of your packages contains a dash too and this confuses pkgtools: the rule is that any of the above variables besides $PKGNAM shouldn't contain dashes.
you should use a slightly different $BUILD$TAG, like "GIT_20200730_ZD" (or even better "20200730_GIT_ZD", where BUILD=20200730_GIT and TAG=_ZD) and you won't have any problem.

1 members found this post helpful.

Thank you Ponce.

I thought I've made a mistake in a package naming.

And off topic - thank you for your package repository. Have you considered to offer you build scripts to public? Would be very helpful, as you compile packages, not be found elsewhere.

Regards.

sorry, are you speaking about this?

https://github.com/Ponce/slackbuilds

no, that:
http://ponce.cc/slackware/slackware64-current/

the packages that you can find in the packages subdirectory (be sure to read the README.txt inside!) are built using the above repository.
the other directories in the link you posted contain mainly old stuff.

Thanks for explanation