[Slackbuilds-users] Fwd: [Slackbuilds-devel] New SBo Upload: msgpack-c-c

[Giancarlo Dessì]

I forward this reply sent to Bob because I would like opinions and/or 
suggestion about this matter. I have no idea how to solve the issue of 
renaming three packages (mgspack-c, msgpack-c-c, and msgpack-c-cpp) that 
are all needed by different slackbuilds but they generate problems 
because the sources are released in the same repository and can do 
conflicts.

Anyone could help me?

Thanks in advanced :-)


-------- Messaggio Inoltrato --------
Oggetto: 	Re: [Slackbuilds-devel] New SBo Upload: msgpack-c-c
Data: 	Thu, 18 Apr 2024 00:08:50 +0200
Mittente: 	Giancarlo Dessì <giandessi at gmail.com>
A: 	B. Watson <urchlay at slackware.uk>, SBo Admin List 
<slackbuilds-devel at slackbuilds.org>




Il 17/04/24 22:36, B. Watson ha scritto:
>
>> Also, you don't need to rename the SlackBuild to msgpack-c-c. The
>> existing build is called msgpack-c, and there are other builds that
>> list it in REQUIRES. Changing the name would require updating all
>> those builds, too. Please don't.
>
> This part still stands: renaming the build is unnecessary and will
> cause a lot of extra work.

Hi, sorry but I'm not sure if I understood, a lot of issues there are 
about these packages. At the moment, in SBo there are three slackbuilds 
for this package.

Until version 3.3, the source of msgpack-c includes both 
implementations, for C and C++. The slackbuild for this version has to 
be maintained since is required by some packages ( 
https://www.slackbuilds.org/advsearch.php?q=msgpack-c&stype=revdep1 ). I 
don't know if these packages can be updated with support of later 
versions of msgpack-c.

Since version 6.0.0 (and newer), the developers have separate the C and 
C++ implementations in two different packages, named respectively 
msgpack-c and msgpack-c-cpp . Recently I added two new slackbuilds

1) msgpack-c-c: this is maintained for the releases >= 6.0.0 that 
include the C implementation only. It is required by neovim

2) msgpack-c-cpp: this is maintained for the releases >= 6.0.0 that 
inclue the C++ implementation only and it is required by mmtf-cpp

The developers release these different package in the same repository 
(msgpack-c) keeping for the new C-only implementation the same name of 
the older versions and this generates a lot of issues. An user reported 
me that the build of msgpack-c-c is at the moment broken: this happens 
because web browsers like Firefox save the source tarball from the old 
download URL as msgpack-c-c-$VERSION.tar.gz and wget (and other clients, 
I think) save it as msgpack-c-$VERSION.tar.gz. So I found an alternative 
URL that works with all clients saving the tarball as 
msgpack-c-$VERSION.tar.gz. But I can't name the slackbuild msgpack-c: 
this name is reserved for the legacy version (3.3). This is very 
frustrating because I don't know how to solve this. A solution could be 
renaming all three packages as following:

1) msgpack-legacy (or msgpack-c-legacy) for the old versions that 
implement C/C++ (msgpack-c 3.3 and earlier)

2) msgpack-c for the new versions that implement only C (msgpack-c 6.0.0 
and later)

3) msgpack-cpp for the new versions that implements only C++ (msgpack-c-cpp)

But all these packages require sources that are release from an unique 
repository ( https://github.com/msgpack/msgpack-c/releases ) with 
incongruences that generate confusion and conflicts depending on the 
client used for download and I'm not sure how to find the best 
solutions! Have you any suggestions about this mess?

Please be patient, I'm a boomer and my brain runs slowly and my English 
is elementary :-)

-- 
*********************************************************
Giancarlo Dessì
https://www.giand.it
https://github.com/giandex

Slackware Linux... because it works!
*********************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240418/69f19619/attachment-0001.htm>