From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
marcin@bis.org.pl, d.lang@abatec.at, buildroot@buildroot.org,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] Indicating upstream status [was: [PATCH] package/bluez5_utils: Fix builds with musl-libc]
Date: Wed, 29 Mar 2023 11:28:55 +0200 [thread overview]
Message-ID: <20230329112855.6110cf8d@windsurf> (raw)
In-Reply-To: <ffed7523-6dbe-6d61-03e7-57cdbc732097@mind.be>
On Wed, 29 Mar 2023 11:06:47 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> Yeah, that's why I propose "Upstream:" - it's generic enough to cover all of
> these cases. The contents can be freeform I think, check-package should just
> check that the Upstream tag is present. And the documentation should give
> examples of the five cases you mention.
Sure.
> The "patch taken from downstream" is the only one which doesn't fit in the
> "Upstream" thing. But it's also a situation we don't really like: we basically
> don't want local patches, and a patch taken from some other distro _is_ a local
> patch.
The reality is that we have such patches (for example to fix musl build
issues), and we somehow have to live with them.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-29 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 13:09 [Buildroot] [PATCH] package/bluez5_utils: Fix builds with musl-libc Florian Fainelli
2023-03-28 20:25 ` Yann E. MORIN
2023-03-29 8:44 ` [Buildroot] Indicating upstream status [was: [PATCH] package/bluez5_utils: Fix builds with musl-libc] Arnout Vandecappelle
2023-03-29 8:50 ` Thomas Petazzoni via buildroot
2023-03-29 9:06 ` Arnout Vandecappelle
2023-03-29 9:28 ` Thomas Petazzoni via buildroot [this message]
2023-03-29 12:39 ` Florian Fainelli
2023-03-30 7:03 ` Arnout Vandecappelle
2023-03-30 12:21 ` Thomas Petazzoni via buildroot
2023-03-30 12:33 ` Arnout Vandecappelle
2023-03-31 7:28 ` Thomas Petazzoni via buildroot
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=20230329112855.6110cf8d@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=d.lang@abatec.at \
--cc=f.fainelli@gmail.com \
--cc=marcin@bis.org.pl \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.