On 06/05/2024 17:46, Brian Inglis via Cygwin-apps wrote:
On 2024-05-06 09:27, Jon Turney via Cygwin-apps wrote:
[...]
Anyhow, double checking that the "right thing" happened here, I notice
that 'unifont' obsoletes 'unifont-debuginfo', which seems a bit weird,
especially since it contains the expected .dbg files etc.
Brian,
Are you sure that's right?
It appears not!
My reasoning was that as unifont-viewer was split out from
unifont-fonts, unifont-viewer-debuginfo would be generated, but it
appears that is not how that works.
Is there any way to make that work, or should I just drop it in the next
release, or a new -RELEASE?
There's only a single debuginfo package generated for each source
package. It's unclear to me that finer granularity would be very useful.
unifont-viewer seems to be just a script, anyhow, so wouldn't have any
useful debug information.
I don't think this is of any great importance, so fixing it in the
next release seems fine.
