From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: protobuf28: drop versioned names and lib subpackages, update to 3.18.0
Date: Wed, 13 Oct 2021 02:29:44 +0200 [thread overview]
Message-ID: <20211013002944.pJUEp-kSC19Smz20P3AqdWfU8XpBR22BmRHo5Byge9I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32984@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]
There's a closed pull request on the void-packages repository
protobuf28: drop versioned names and lib subpackages, update to 3.18.0
https://github.com/void-linux/void-packages/pull/32984
Description:
In a [discussion a year ago](https://github.com/void-linux/void-packages/pull/18691), I proposed dropping versioned libs subpackages and the consensus was that the versioning should be kept. Since then, protobuf has been updated several times and we've always been able to migrate all dependants, so there's no need to keep the versioned packages around just in case that can't happen some day.
Let's drop the versioned packages to make upgrades easier and avoid polluting repo indexes with old packages that don't get cleaned. Users who need old versions of the libs for un-packaged software may need to build those old versions by hand, but this is just one of the pitfalls of using a rolling Linux distribution.
Another argument was about staging the repo, but that really shouldn't be an issue. Either everything gets moved to the new version or we have to split an protobuf version if there is a breaking incompatibility.
@Hoshpak you originally argued in favor of keeping the versioned naming. @the-maldridge I don't know if you cared one way or another, but you were the maintainer at the time. @q66 and @ericonr both seemed receptive to this proposal a few months back on IRC, so I invite them to weigh in.
prev parent reply other threads:[~2021-10-13 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 19:24 [PR PATCH] Protobuf ahesford
2021-09-18 0:15 ` protobuf28: drop versioned names and lib subpackages, update to 3.18.0 ericonr
2021-10-06 19:56 ` [PR PATCH] [Updated] " ahesford
2021-10-12 20:15 ` ahesford
2021-10-13 0:29 ` ahesford
2021-10-13 0:29 ` ahesford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211013002944.pJUEp-kSC19Smz20P3AqdWfU8XpBR22BmRHo5Byge9I@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).