Re: msgpack-git upgrade question

[Mayuresh <mayuresh%acm.org@localhost>]

On Mon, Sep 23, 2024 at 02:26:32PM +0200, Thomas Klausner wrote:
> wip/msgpack-git is the same software as devel/msgpack, just a git
> snapshot of it.

Ok, will keep the name same. But I have these observations:

The upstream packages seem to be tagged separately for c and c++ under the
same github project msgpack-c. (For other languages they have separate
projects.)

https://github.com/msgpack/msgpack-c/tags

E.g. c-6.1.0, cpp-6.1.1 etc, these are interleaved.

So keeping in line with the upstream convention, and also pkgsrc's
existing nomenclature such as php-msgpack, py-msgpack, ruby-msgpack etc.
should we have have c-msgpack and cpp-msgpack?

Alternatively, leave the legacy name msgpack to imply c-msgpack and rename
wip/msgpack-git to wip/cpp-msgpack?

As such there are several situations where one upstream project spawns
into multiple pkgsrc packages - often based on configuration options, here
based on tags.

(Upstream should ideally make this a configuration option instead of
being identified by tags. But that apart.)

-- 
Mayuresh