On Tue, Nov 12, 2024 at 09:29:02AM -0000, Germano Massullo wrote: > Hello, I found out this old thread while searching for Fedora packaging guidelines for Git submodules. > Are there any news about guidelines on how to deal with them? I could not find any information on docs.fedoraproject.org > I am currently dealing with this submodule > https://github.com/web-eid/web-eid-app/tree/main/lib > I think I should just treat it as a bundled library and trying to unbundle it by creating a separate package Whether upstream has used a git submodule, vs deep copying the 3rd party code into their repo, is largely irrelevant to Fedora, as we're not working directly with upstream git repositories, we're using tarballs in the RPM build. IOW, if the 3rd party code ends up in the source tarball that Fedora is building from, then the "bundled library" packaging guidelines apply. Even if the git submodule code ends up in separate source tarballs, to be used alongside the main source tarball, the "bundled library" guidelines should still apply. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- _______________________________________________ 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