<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>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.</p>
<p>Anyone could help me?</p>
<p>Thanks in advanced :-)</p>
<div class="moz-forward-container"><br>
-------- Messaggio Inoltrato --------
<table class="moz-email-headers-table" cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Oggetto:
</th>
<td>Re: [Slackbuilds-devel] New SBo Upload: msgpack-c-c</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Data: </th>
<td>Thu, 18 Apr 2024 00:08:50 +0200</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Mittente:
</th>
<td>Giancarlo Dessì <a class="moz-txt-link-rfc2396E" href="mailto:giandessi@gmail.com"><giandessi@gmail.com></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">A: </th>
<td>B. Watson <a class="moz-txt-link-rfc2396E" href="mailto:urchlay@slackware.uk"><urchlay@slackware.uk></a>, SBo Admin List
<a class="moz-txt-link-rfc2396E" href="mailto:slackbuilds-devel@slackbuilds.org"><slackbuilds-devel@slackbuilds.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
Il 17/04/24 22:36, B. Watson ha scritto:<br>
<blockquote type="cite"><br>
<blockquote type="cite">Also, you don't need to rename the
SlackBuild to msgpack-c-c. The<br>
existing build is called msgpack-c, and there are other builds
that<br>
list it in REQUIRES. Changing the name would require updating
all<br>
those builds, too. Please don't.<br>
</blockquote>
<br>
This part still stands: renaming the build is unnecessary and
will<br>
cause a lot of extra work.<br>
</blockquote>
<br>
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.<br>
<br>
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 (
<a class="moz-txt-link-freetext" href="https://www.slackbuilds.org/advsearch.php?q=msgpack-c&stype=revdep1">https://www.slackbuilds.org/advsearch.php?q=msgpack-c&stype=revdep1</a>
). I don't know if these packages can be updated with support of
later versions of msgpack-c.<br>
<br>
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<br>
<br>
1) msgpack-c-c: this is maintained for the releases >= 6.0.0
that include the C implementation only. It is required by neovim<br>
<br>
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<br>
<br>
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:<br>
<br>
1) msgpack-legacy (or msgpack-c-legacy) for the old versions that
implement C/C++ (msgpack-c 3.3 and earlier)<br>
<br>
2) msgpack-c for the new versions that implement only C (msgpack-c
6.0.0 and later)<br>
<br>
3) msgpack-cpp for the new versions that implements only C++
(msgpack-c-cpp)<br>
<br>
But all these packages require sources that are release from an
unique repository ( <a class="moz-txt-link-freetext" href="https://github.com/msgpack/msgpack-c/releases">https://github.com/msgpack/msgpack-c/releases</a>
) 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?<br>
<br>
Please be patient, I'm a boomer and my brain runs slowly and my
English is elementary :-)<br>
<br>
<pre class="moz-signature">--
*********************************************************
Giancarlo Dessì
<a class="moz-txt-link-freetext" href="https://www.giand.it">https://www.giand.it</a>
<a class="moz-txt-link-freetext" href="https://github.com/giandex">https://github.com/giandex</a>
Slackware Linux... because it works!
*********************************************************
</pre>
</div>
</body>
</html>