> so you are special-casing packages that have /usr/bin/mono.
> Why not simply manually add a [ .spec file change]
oh - well, this is not very simple when you have to add it to a lot of packages (60 or so) - and in general, some pleasant way to drop (known to be) debuginfo information automatically into -debuginfo files is surely more pleasant ? This presumably is the thinking underlying a central find-debuginfo.sh script.
The check for /usr/bin/mono - is not intended to make this specific to a single package - but to make it specific to those packages that have a BuildRequires of mono - ie. to reduce any chance of false positives with people calling their files "foo.dll.mdb" but them not being either a DLL or a debuginfo file ;-) I tend to think that is pretty unlikely, and in these cases they would want those files in a -debuginfo file anyway - so we could easily remove that.
Hi Richard !
> so you are special-casing packages that have /usr/bin/mono.
> Why not simply manually add a [ .spec file change]
oh - well, this is not very simple when you have to add it to a lot of packages (60 or so) - and in general, some pleasant way to drop (known to be) debuginfo information automatically into -debuginfo files is surely more pleasant ? This presumably is the thinking underlying a central find-debuginfo.sh script.
The check for /usr/bin/mono - is not intended to make this specific to a single package - but to make it specific to those packages that have a BuildRequires of mono - ie. to reduce any chance of false positives with people calling their files "foo.dll.mdb" but them not being either a DLL or a debuginfo file ;-) I tend to think that is pretty unlikely, and in these cases they would want those files in a -debuginfo file anyway - so we could easily remove that.