I am not aware of a specific policy of where to keep embedded libraries. Although I'm newish to Debian so take that with a grain of salt...
Packages like freebayes include extra embedded external libraries in debian/ext: https://sources.debian.org/src/freebayes/1.3.9-1/debian/ext Not sure how accepted this is, but given the context of recast, it seems at least defendable. Godot has its own copy of recastnavigation in thirdparty/ so I don't need to add an extra copy. In any case, I don't think packages should be fetching sources from the internet at build time, but I can't find an explicit policy against it. My understanding was buildd was only recently isolated to more strictly enforce the no external network access convention at build time, so I doubt they will revert. Best, Travis On Mon, Sep 22, 2025 at 03:22:20PM +0200, bret curtis wrote: > Another question for the group, it was suggested that another solution > instead of embedding recast into the repo. Is there a way to clone the repo > to a directory and tell cmake to use that for building? > > Apparently buildd is network isolated, so our cmake fetch won't work. Or > has that changed recently? > > Cheers, > Bret > > On Mon, Sep 22, 2025 at 11:01 AM bret curtis <[email protected]> wrote: > > > Hey gang! > > > > Thank you for the replies. > > > > We've (OpenMW) been contributing upstream but development seems to have > > stopped. We're still hopeful but with 26 open PRs, infrequent updates and > > lack of communication we're considering doing a fork of the project. > > > > I'll add the Breaks dependency and update the package names accordingly. > > > > We can still debate if it's worth having in Debian or as you said, just > > use the embedded recastnavigation. > > > > Cheers, > > Bret > > > > > > > > On Sat, Sep 20, 2025 at 6:12 PM Travis Wrightsman <[email protected]> > > wrote: > > > >> Hi all, > >> > >> Thanks for working on this Bret! > >> > >> For what it's worth, I am planning on reverting Godot back to its > >> embedded recastnavigation copy because this upstream recommends using it > >> this way [0] (which is supported by Debian policy [1]) and they > >> basically told me in the linked upstream bug report that they don't make > >> any ABI promises. > >> > >> Personally, it doesn't seem worth it to fight upstream by providing a > >> shared library for recast in Debian? On the other hand, they don't seem > >> to release that often, so maybe it isn't that much of a pain. > >> > >> Cheers, > >> Travis > >> > >> [0] > >> https://github.com/recastnavigation/recastnavigation/blob/main/Docs/_2_BuildingAndIntegrating.md#building--integrating > >> [1] > >> https://www.debian.org/doc/debian-policy/ch-source.html#embedded-code-copies > >> > >
