From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Vincent Davis Jr <vince@underview.tech>
Cc: docs@lists.yoctoproject.org,
Richard Purdie <richard.purdie@linuxfoundation.org>,
quentin.schulz@theobroma-systems.com
Subject: Re: [docs] [PATCH] ref-manual/system-requirements.rst: support Arch Linux
Date: Mon, 2 Jan 2023 11:30:49 +0100 [thread overview]
Message-ID: <d3110d81-b0fa-de4a-965a-0c775485e7dd@bootlin.com> (raw)
In-Reply-To: <456184cf-b08c-9eeb-c261-840552bcb5dc@theobroma-systems.com>
Hi Vincent
Thanks for the patch anyway! I was also going to check whether Arch was
tested by our Autobuilder.
Am 02.01.23 um 11:19 schrieb Quentin Schulz via lists.yoctoproject.org:
> Hi Vincent,
>
> Thanks for your patch.
>
> I'm afraid this will not be accepted. We usually refuse to advertise
> support for rolling release distributions.
>
> The advertised supported distributions are tested on our autobuilder
> and we don't run ArchLinux there. I would expect we also don't have
> the bandwidth to debug when things break in ArchLinux. Note that we
> also do not specify support for derivatives of Debian or Ubuntu
> distributions, we have seen issues with Pop_OS! in the past for example.
>
> For this to be accepted in the documentation, I believe we'd need
> patches for the autobuilder so that some builds run on an ArchLinux
> server. This probably needs to be discussed (and financially
> supported?) with Michael Halstead our sysadmin. But first and
> foremost, we would need this support to be agreed by maintainer(s),
> hence why I'm Cc'ing Richard on this, who I hope can raise this to the
> proper board if he doesn't veto this.
>
> Considering it's holiday season, please expect some delay, but don't
> hesitate to ping us in a week or two were you to not receive an answer
> meanwhile.
Another idea would be to create a page on our wiki
(https://wiki.yoctoproject.org/), for people trying to use Yocto on
distributions which are currently not supported. We could then refer to
such a page from the documentation, reminding people that there is no
support commitment. Or something specific to Arch would be to update
https://wiki.archlinux.org/title/Yocto
Just my two cents.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-01-02 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 19:49 [PATCH] ref-manual/system-requirements.rst: support Arch Linux Vincent Davis Jr
2023-01-02 10:19 ` [docs] " Quentin Schulz
2023-01-02 10:30 ` Michael Opdenacker [this message]
2023-01-02 10:33 ` Alexander Kanavin
[not found] ` <17367770FC1C1495.4716@lists.yoctoproject.org>
2023-01-02 12:58 ` Alexander Kanavin
2023-01-05 15:24 ` Michael Opdenacker
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=d3110d81-b0fa-de4a-965a-0c775485e7dd@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=vince@underview.tech \
/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