[Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague)

[Andrzej Telszewski]

*From: *Konrad J Hambrick <kjhambrick at gmail.com>
*To: *SlackBuilds.org Users List <slackbuilds-users at slackbuilds.org>
*Date: *8 Apr 2023 12:56:36
*Subject: *Re: [Slackbuilds-users] LibreOffice vs libreoffice (confusing, too vague)

> On Sat, Apr 8, 2023 at 4:54 AM marav <marav8 at free.fr> wrote:
>> 
>> I for one, I think all binary packages should be renamed with *-bin
>> 
>> It gives the most important information that the slackbuild is not a compiled version, directly in the name
>> No matter if there is a compiled version or not
>> 
> All --
> 
> Thinking out loud here ...
> 
> I agree with marav but would there not need to be special, one-time instructions to `removepkg old-package-without-dash-bin` before doing an `upgradepkg --install-nre new-package-with-bin` ?
> 
> Othewise, wouldn't upgradepkg be confused ? 
> 
> And would /var/log/packages/ be 'corrupted' ?
> 
> -- kjh


`pkgtools` are (specifically) designed in a way that if one package over-installs another, there is no corruption in the database.

You just need to uninstall the old package, which can be safely done after the new package is installed.

Actually, this is how the `upgradepkg` works under the hood.
It over-installs one package on the other, then removes the old one.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230408/0a4d8866/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 691 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230408/0a4d8866/attachment.asc>