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

List:       debian-devel
Subject:    Re: Another take on package relationship substvars
From:       IOhannes_m_zmölnig <umlaeute () debian ! org>
Date:       2024-02-22 19:52:36
Message-ID: 52496F4C-8A15-4963-BD3A-7F10965E1682 () debian ! org
[Download RAW message or body]

Am 22. Februar 2024 20:25:32 MEZ schrieb Boyuan Yang <byang@debian.org>:
>在 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}?


While I like the idea in general, I wonder how I could override these automatic additions.
I think there are some packages that even demote `${shlibs:Depends}` to Recommends.


mfh.her.fsr
IOhannes

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