[prev in list] [next in list] [prev in thread] [next in thread] 

List:       debian-devel
Subject:    Re: Another take on package relationship substvars
From:       Boyuan Yang <byang () debian ! org>
Date:       2024-02-22 19:25:32
Message-ID: 26686f2dfb2ac004dccab64a5c9a24fc873c1021.camel () debian ! org
[Download RAW message or body]


在 2024-02-22星期四的 19:32 +0100，Niels Thykier写道：
> I think our package helper tooling should just automatically aggregate 
> all provided substvars of the format ${*:Depends} and append it the 
> Depends field. Rinse and repeat for other relationship fields.
> 
> The list of fields where this is applied would be curated, so it only 
> applies to known relationship fields where we feel it makes sense. My 
> starting list would be:
> 
>    * Any dependency field, that is: Pre-Depends, Depends, Recommends, and
>        Suggests
> 
>    * The Provides field.
> 
> I am omitting Breaks, Conflicts, and Replaces because I am not aware of 
> any users of these at the moment. I am open to adding them, if there is 
> a strong use-case.

Can we also consider ${*:Built-Using} as typically seen in ${sphinxdoc:Built-Using}?
This is another field that people keep forget adding. While missing
this field is not severely harmful, having it automatically handled
would be beneficial.

Thanks,
Boyuan Yang

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]