How to handle submodules that are not packaged
- To: SmartList <debian-mentors@lists.debian.org>
- Subject: How to handle submodules that are not packaged
- From: David James <davidjamescastor215@proton.me>
- Date: Sat, 17 Feb 2024 21:31:22 +0000
- Message-id: <-6jAy4_uSP4W19br9h5GAJQX56ho8oVLFNO8zD0hn3ZXxS3xcWSBaxu3ynLmc1Qn1P3np-lrz0RdxmvyRNEVf6WHFLrjGf7vMGs0_sbLZzQ=@proton.me>
Dear Mentors,
I have been looking for information on how to handle the submodule of a project that is not or cannot be packaged for Debian. Say a project I want to package has the submodule registered at externals/foo/bar. For whatever reason Bar doesn't exist in the repositories. How do I handle this as a packager?
To give an actual example of what I mean, the upstream yuzu repository (https://github.com/yuzu-emu/yuzu) has a submodule at externals/sirit. The yuzu package moves this into the top directory with a rule in debian/rules that creates a symbolic link in externals/.
As yuzu is the only real example I can find of this situation, I was wondering if there are any other ways to handle this. More importantly, if there are other ways how would they be handled on the Salsa side i.e. a package repository with upstream/ and debian/ branches?
Any insight would be greatly appreciated.
Regards,
David James
Reply to: