All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <quentin.schulz@cherry.de>, "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "YP docs mailing list" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] ref-manual: clarify that PACKAGE_EXCLUDE supports DEB packaging
Date: Tue, 26 May 2026 09:48:02 +0200	[thread overview]
Message-ID: <DISFY9Q6CGSZ.TT46F4NAJSFC@bootlin.com> (raw)
In-Reply-To: <36d0ec5d-8965-44fd-8886-ac3a014d6fab@cherry.de>

Hi,

On Fri May 22, 2026 at 6:23 PM CEST, Quentin Schulz via lists.yoctoproject.org wrote:
> On 5/22/26 6:26 PM, Robert P. J. Day wrote:
>> On Fri, 22 May 2026, Quentin Schulz wrote:
>> 
>>> Hi Robert,
>>>
>>> On 5/22/26 6:15 PM, Robert P. J. Day via lists.yoctoproject.org wrote:
>>>>
>>>> As an accompaniment to earlier commit
>>>> 0d05dedd62a6d4c726f120a23654ede1f0b23d8e, correct that the
>>>> PACKAGE_EXCLUDE supports the DEB packaging backend.
>>>>
>>>> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>>>>
>>>> ---
>>>>
>>>> diff --git a/documentation/ref-manual/variables.rst
>>>> b/documentation/ref-manual/variables.rst
>>>> index c65794229..2773e9864 100644
>>>> --- a/documentation/ref-manual/variables.rst
>>>> +++ b/documentation/ref-manual/variables.rst
>>>> @@ -6927,8 +6927,8 @@ system and gives an overview of their function and
>>>> contents.
>>>>          an iterative development process to remove specific components from
>>>> a
>>>>          system.
>>>>
>>>> -      This variable is supported only when using the IPK and RPM
>>>> -      packaging backends. DEB is not supported.
>>>> +      This variable is supported by all of the RPM, DEB and IPK
>>>> +      packaging backends.
>>>>
>>>
>>> Considering those are all the backends we support, can't we simply remove the
>>> paragraph entirely?
>> 
>>    i mentally flipped a coin and thought about people who might have
>> remembered the earlier situation, but i'm happy to toss that last line
>> entirely.
>> 
>
> Fine either way, let's see what Antonin prefers :)

Considering both options, I think they are for the most part equal, except that
someone who did know about the limitation before will now have a clear sentence
that clarifies this point now. So let's keep it, I'm taking the patch :)

Antonin


      reply	other threads:[~2026-05-26  7:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 16:19 [PATCH] ref-manual: clarify that PACKAGE_EXCLUDE supports DEB packaging Robert P. J. Day
2026-05-22 16:20 ` [docs] " Quentin Schulz
2026-05-22 16:26   ` Robert P. J. Day
2026-05-22 16:23     ` Quentin Schulz
2026-05-26  7:48       ` Antonin Godard [this message]

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=DISFY9Q6CGSZ.TT46F4NAJSFC@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=rpjday@crashcourse.ca \
    /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.