From: flexibeast <flexibeast@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Manual.md: Note when `archs` should be used.
Date: Sun, 16 Aug 2020 02:30:59 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24302@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
There is a new pull request by flexibeast against master on the void-packages repository
https://github.com/flexibeast/void-packages archs
https://github.com/void-linux/void-packages/pull/24302
Manual.md: Note when `archs` should be used.
A patch file from https://github.com/void-linux/void-packages/pull/24302.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-archs-24302.patch --]
[-- Type: text/x-diff, Size: 767 bytes --]
From 8b6b3bade08e7f49b219ac0bf57a81bbfa1b3635 Mon Sep 17 00:00:00 2001
From: Alexis <flexibeast@gmail.com>
Date: Sun, 16 Aug 2020 10:29:19 +1000
Subject: [PATCH] Manual.md: Note when `archs` should be used.
---
Manual.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Manual.md b/Manual.md
index ab13b1c38e9..e6d44a2352a 100644
--- a/Manual.md
+++ b/Manual.md
@@ -704,6 +704,8 @@ used.
- `archs` Whitespace separated list of architectures that a package can be
built for, available architectures can be found under `common/cross-profiles`
alongside the `noarch` value for packages that do not contain any machine code.
+This should only be used when upstream explicitly states that their software only works
+on specific architectures.
Examples:
```
next reply other threads:[~2020-08-16 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 0:30 flexibeast [this message]
2020-08-16 23:34 ` [PR REVIEW] " ahesford
2020-08-16 23:55 ` [PR PATCH] [Updated] " flexibeast
2020-08-16 23:57 ` [PR REVIEW] " flexibeast
2020-08-17 0:02 ` [PR PATCH] [Merged]: " ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24302@inbox.vuxu.org \
--to=flexibeast@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).