From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] glibc: update to 2.38.
Date: Wed, 09 Aug 2023 15:46:40 +0200 [thread overview]
Message-ID: <20230809134640.4b7NNx_dvvisyqIRrsbyfxxFvlxPQibCgDvYYcwa_TM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45501@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/45501#issuecomment-1671358942
Comment:
The `compat` build option in `libxcrypt` should be removed. Either the template provides the `-compat` package or it doesn't. Build options are generally a bad idea, and they exist mostly as a hack around arch-dependent compatibility or a way to let people build packages with different configurations. In `libxcrypt`, all the build option does is change what packages are built, not how they are built, at the expense of making the template more difficult to understand.
That said, I don't know if there is value in providing the `-compat` library at all. If we have restricted packages (or others that just repackage upstream binaries) that require the ABI, then I guess we should provide it. If there are none, adding complexity to the template and generally increasing maintenance burden just so somebody can download legacy binaries from the web doesn't seem worthwhile. Binary compatibility with other distributions is a bonus when it works, but is not a project goal.
next prev parent reply other threads:[~2023-08-09 13:46 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 0:09 [PR PATCH] " oreo639
2023-08-09 0:21 ` [PR PATCH] [Updated] " oreo639
2023-08-09 0:49 ` oreo639
2023-08-09 13:46 ` ahesford [this message]
2023-08-09 21:55 ` oreo639
2023-08-09 21:57 ` oreo639
2023-08-30 17:06 ` [PR PATCH] [Updated] " oreo639
2023-08-30 17:14 ` oreo639
2023-08-30 17:15 ` oreo639
2023-08-30 19:42 ` oreo639
2023-08-30 19:47 ` oreo639
2023-08-31 2:10 ` oreo639
2023-08-31 5:22 ` oreo639
2023-08-31 5:27 ` oreo639
2023-09-14 21:28 ` oreo639
2023-09-14 22:20 ` oreo639
2023-09-14 22:21 ` oreo639
2023-09-19 22:19 ` [PR PATCH] [Updated] " oreo639
2023-09-20 5:25 ` oreo639
2023-09-20 17:29 ` oreo639
2023-09-27 17:13 ` oreo639
2023-09-27 17:28 ` oreo639
2023-09-29 19:59 ` oreo639
2023-10-04 17:36 ` oreo639
2023-10-05 21:07 ` oreo639
2023-10-08 18:54 ` oreo639
2023-10-09 21:15 ` oreo639
2023-10-09 21:15 ` oreo639
2023-10-11 18:23 ` oreo639
2023-10-14 21:16 ` oreo639
2023-10-16 17:29 ` oreo639
2023-10-20 21:28 ` oreo639
2023-10-27 23:35 ` oreo639
2023-10-28 3:17 ` [PR PATCH] [Updated] " oreo639
2023-10-28 3:48 ` oreo639
2023-10-28 3:48 ` oreo639
2023-10-31 2:43 ` oreo639
2023-11-01 19:57 ` oreo639
2023-11-03 23:06 ` oreo639
2023-11-06 6:32 ` oreo639
2023-11-13 19:29 ` oreo639
2023-11-14 2:32 ` oreo639
2023-11-14 22:19 ` oreo639
2023-11-25 0:16 ` oreo639
2023-11-29 18:29 ` oreo639
2023-12-02 22:03 ` oreo639
2023-12-06 20:47 ` oreo639
2023-12-07 4:49 ` oreo639
2023-12-11 9:26 ` classabbyamp
2023-12-11 9:26 ` classabbyamp
2023-12-11 9:30 ` oreo639
2023-12-11 9:31 ` oreo639
2023-12-11 9:31 ` oreo639
2023-12-11 9:32 ` oreo639
2023-12-11 9:46 ` classabbyamp
2023-12-11 9:50 ` oreo639
2023-12-11 12:39 ` oreo639
2023-12-11 13:02 ` [PR PATCH] [Updated] " oreo639
2023-12-11 13:02 ` oreo639
2023-12-11 13:59 ` leahneukirchen
2023-12-11 15:25 ` oreo639
2023-12-11 15:26 ` oreo639
2023-12-11 15:30 ` oreo639
2023-12-11 15:34 ` leahneukirchen
2023-12-11 15:36 ` oreo639
2023-12-20 0:32 ` [PR PATCH] [Updated] " oreo639
2023-12-21 3:24 ` oreo639
2023-12-22 2:10 ` oreo639
2023-12-23 11:37 ` [PR REVIEW] " leahneukirchen
2023-12-23 11:40 ` leahneukirchen
2023-12-23 22:10 ` oreo639
2023-12-23 22:12 ` oreo639
2023-12-23 22:15 ` oreo639
2023-12-23 22:17 ` oreo639
2023-12-23 22:19 ` oreo639
2023-12-23 22:21 ` oreo639
2023-12-24 2:02 ` oreo639
2023-12-25 3:03 ` [PR PATCH] [Updated] " oreo639
2023-12-25 3:32 ` [PR REVIEW] " oreo639
2023-12-25 3:33 ` oreo639
2023-12-25 19:09 ` [PR PATCH] [Merged]: " classabbyamp
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=20230809134640.4b7NNx_dvvisyqIRrsbyfxxFvlxPQibCgDvYYcwa_TM@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).