From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [wip] common: disable creation of noarch packages.
Date: Thu, 20 Aug 2020 01:10:08 +0200 [thread overview]
Message-ID: <20200819231008.d6UpEWwDHKZT2oJjNV70PBk4ChUU4FQRXDAr9UV1szw@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: 1248 bytes --]
New comment by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/pull/24357#issuecomment-676800808
Comment:
Ok, replying to some comments here:
@ericonr:
> I like noarch because it enables me to build something like the void-docs package and put it in the release so that everyone can download it as a preview. @zdykstra does the same thing with zfsbootmenu, where it's even more useful because he does release candidates.
What do you mean? I don't really understand this use-case. Is the idea you build once and then `XBPS_TARGET_ARCH=x86_^4-musl xbps-rindex -a *.xbps` for each architecture? Doing things like this is completely unsupported AFAICT.
Removing noarch building from the build system entirely removes the need for noarch support in xbps, which is quite broken.
@ahesford
> That noarch implies nodebug, nostrip, noshlibprovides and whatever else does not make it a useful shorthand for those things, because it also implies other things that are being disregarded by dropping current noarch functionality.
I don't quite get what you mean. These other things are unnessecary, and the shorthand for `nodebug`, etc is useful for data packages. This is why I think we shouldr ename it.
next prev parent reply other threads:[~2020-08-19 23:10 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 [this message]
2020-08-19 23:21 ` the-maldridge
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=20200819231008.d6UpEWwDHKZT2oJjNV70PBk4ChUU4FQRXDAr9UV1szw@z \
--to=fosslinux@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).