On 12/9/25 12:03 PM, Gary Buhrmaster wrote:
> On Tue, Dec 9, 2025 at 4:22 PM Dave Cantrell <[email protected]> wrote:
> 
>> Right, but what I was wanting was for complete support for doing that so 
>> that things like --verify work.  Also, for a user to be able to bring in 
>> not-installed files later if they want to.  Possibly more explicit 
>> integration in higher up tools like dnf.  But yeah, doing this is not 
>> difficult.
>>
>> I also want to think about packaging policy in addition to the tooling, 
>> which is where my brain was going for a lot of what I said.
> 
> While the current guidelines specify one
> should include the man pages, perhaps
> (like the -docs subpackage), one might
> think about a -man subpackage that
> the main package Recommends.
> 
> And perhaps, to make it easier, suggest
> one uses something of the form
>   Recommends: (foo-man if man-db)?

man subpackages are a thing I was recommending against.  It makes sense for 
libraries that provide section 3 man pages for lots of functions, but if I 
install coreutils I kind of also expect to get the man page for ls.  This ends 
up with the current practice of "if it's a lot of docs, make a subpackage."  
But we don't really define a lot because it's hard to.

I would like to see fewer packages in general and instead have functionality in 
the tools that allow you to construct systems with the docs you want and don't 
want without having to have lists of lots of man page subpackages to include or 
exclude.  But that's just me.

-- 
David Cantrell <[email protected]>
Red Hat, Inc. | Boston, MA | EST5EDT

-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to