I noticed this thread, I develop a personal project where I use about 10
C libraries, I noticed that "glfw", "libsodium" and "libevent" do not
have their corresponding mingw packages. I was considering trying to
package them but unifying them with the native packages would be better.
Of course, this would put more pressure on the maintainers.
I could however open a PR to add them to the native packages. Do we have
some libraries where this unification is already finished so that I
could take inspiration?
On 24. 8. 2022 16:00, Daniel P. Berrangé wrote:
On Wed, Aug 24, 2022 at 03:57:37PM +0200, Fabio Valentini wrote:
On Wed, Aug 24, 2022 at 3:49 PM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote:
On Sun, Feb 20, 2022 at 10:13:18PM +0100, Sandro Mani wrote:
Hi
Following recent discussions and to reduce the maintenance burden, I'm
planning to start merging native and mingw packages. Initially, I'll be
looking at these packages where I maintain both variants:
I've done the same with all the mingw packages I maintained just
before Fedora 37 branched. So the following native packages now
just contain mingw sub-RPMs:
libvirt, libvirt-glib, libosinfo, osinfo-db, osinfo-db-tools, gtk-vnc
I'm so happy to have reduced this maint burden. I see a few new mingw
packages pending in package review and think it'd be nice to first ask
the native maintainer to consider unified package, before we approve
any new separate mingw packages.
Our Mingw packaging guidelines, however, exclusively describe fully
separated mingw packages. So if I suggest this to a native package
maintainer who is not already familiar with mingw, they would be
right to question whether this is a desirable thing.
IOW, I think we need to look at getting the mingw packaging docs
updated to promote unified packaging as an officially supported
(and even preferred) option, alongside separate packaging.
Sounds great.
The Packaging Committee is looking forward to your PR ;)
I don't want to rush into doing that myself in case someone else reading
along is very enthusiastic to do the work themselves ;-P
With regards,
Daniel
--
Marián Konček
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
