From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [wip] common: disable creation of noarch packages.
Date: Thu, 20 Aug 2020 01:21:24 +0200 [thread overview]
Message-ID: <20200819232124.P9gANusal-kSVDJuFaive3OHpt8zDROgBVD-dpL6isY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24357@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
New comment by the-maldridge on void-packages repository
https://github.com/void-linux/void-packages/pull/24357#issuecomment-676805631
Comment:
Primary advantages with noarch
* it saves a meager amount of disk space that we're somehow still worried about in 2020 when you can buy commodity 10T disks at reasonable prices delivered to your DC of choice in around 2 days.
Primary disadvantages of noarch
* pretty much everything else about it.
In no particular order noarch relies on kludges within xbps itself, it makes managing the repos unnecessarily complicated, it makes it shockingly difficult to construct a coherent package graph that could be used to schedule builds in a distributed fashion (along with our kludgy multilib, but that's another story).
As far as timeline to drop noarch from xbps? As soon as it is practically feasible. Removing that code would be on the critical path to improving the dependency solver and generally making xbps more robust. I would go so far as to propose a bulk rebuild of all current noarch packages to make it possible to dump the support from xbps sooner.
I disagree that there is no need to touch templates. It makes sense to remove the components that trigger this behavior to minimize confusion. We are not intending to support it, so we should not keep the detritus in place that suggests we do.
next prev parent reply other threads:[~2020-08-19 23:21 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 6:51 [PR PATCH] " fosslinux
2020-08-19 12:23 ` ericonr
2020-08-19 12:38 ` ahesford
2020-08-19 12:46 ` ahesford
2020-08-19 13:03 ` Chocimier
2020-08-19 14:48 ` q66
2020-08-19 15:24 ` ahesford
2020-08-19 15:43 ` q66
2020-08-19 15:45 ` q66
2020-08-19 16:10 ` ahesford
2020-08-19 17:15 ` q66
2020-08-19 17:17 ` ericonr
2020-08-19 17:19 ` q66
2020-08-19 23:05 ` fosslinux
2020-08-19 23:10 ` fosslinux
2020-08-19 23:21 ` the-maldridge [this message]
2020-08-19 23:28 ` fosslinux
2020-08-19 23:30 ` the-maldridge
2020-08-20 0:24 ` q66
2020-08-20 0:38 ` fosslinux
2020-08-20 0:44 ` sgn
2020-08-20 0:44 ` sgn
2020-08-20 0:46 ` ericonr
2020-08-20 0:51 ` sgn
2020-08-20 0:56 ` fosslinux
2020-08-20 1:00 ` ahesford
2020-08-20 1:08 ` ericonr
2020-08-20 2:05 ` the-maldridge
2020-08-20 6:29 ` fosslinux
2020-08-20 6:32 ` fosslinux
2020-08-20 12:52 ` ericonr
2020-08-20 17:55 ` the-maldridge
2020-08-20 23:09 ` fosslinux
2020-08-21 22:26 ` [PR PATCH] [Updated] " fosslinux
2020-08-21 22:27 ` fosslinux
2020-08-21 22:29 ` [PR PATCH] [Updated] " fosslinux
2020-08-21 22:29 ` fosslinux
2020-08-24 23:49 ` fosslinux
2020-08-24 23:50 ` fosslinux
2020-08-24 23:50 ` fosslinux
2020-08-25 19:47 ` [PR REVIEW] " Chocimier
2020-08-25 19:49 ` Chocimier
2020-08-25 20:02 ` ericonr
2020-08-25 20:19 ` [PR REVIEW] " Chocimier
2020-08-25 22:55 ` fosslinux
2020-08-25 22:58 ` fosslinux
2020-08-27 7:22 ` [PR PATCH] [Updated] " fosslinux
2020-08-27 7:22 ` fosslinux
2020-08-27 7:23 ` fosslinux
2020-08-27 20:21 ` [PR REVIEW] " Chocimier
2020-08-27 20:28 ` Chocimier
2020-08-28 0:41 ` [PR REVIEW] " fosslinux
2020-08-28 0:43 ` fosslinux
2020-08-28 0:45 ` sgn
2020-08-28 1:07 ` fosslinux
2020-09-02 0:40 ` fosslinux
2020-09-02 0:40 ` fosslinux
2020-09-02 0:40 ` [PR REVIEW] " fosslinux
2020-09-03 23:47 ` fosslinux
2020-09-04 11:41 ` fosslinux
2020-09-04 11:44 ` fosslinux
2020-09-04 13:24 ` ahesford
2020-09-04 22:59 ` fosslinux
2020-09-04 23:17 ` fosslinux
2020-09-04 23:19 ` [PR PATCH] [Updated] " fosslinux
2020-09-04 23:19 ` [PR REVIEW] " fosslinux
2020-09-05 7:00 ` Chocimier
2020-09-05 7:16 ` fosslinux
2020-10-31 6:49 ` fosslinux
2020-10-31 6:49 ` fosslinux
2020-10-31 6:49 ` fosslinux
2020-10-31 6:49 ` fosslinux
2020-11-30 14:57 ` sgn
2020-11-30 16:37 ` sgn
2020-12-01 12:47 ` sgn
2020-12-05 10:17 ` sgn
2020-12-05 10:17 ` sgn
2020-12-15 11:26 ` fosslinux
2020-12-26 2:47 ` sgn
2020-12-26 2:48 ` sgn
2020-12-26 2:48 ` sgn
2020-12-26 2:48 ` sgn
2020-12-26 6:34 ` sgn
2020-12-26 6:42 ` sgn
2020-12-26 11:04 ` sgn
2020-12-26 11:04 ` sgn
2020-12-27 14:31 ` sgn
2021-01-20 12:34 ` [PR PATCH] [Closed]: " q66
2021-01-20 21:47 ` fosslinux
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=20200819232124.P9gANusal-kSVDJuFaive3OHpt8zDROgBVD-dpL6isY@z \
--to=the-maldridge@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).