On Mon, Jul 14, 2025 at 10:46:35AM +0500, Ilya Orlov wrote:
Ah, I see. So with this policy it would be ok to embed: wlroots and reshade - because it's forks made specifically to be used in gamescope submodules.
No, only if the original wlroots and reshade projects were ones that were intended to be used via vendoring/embedding.
Again, if the policy clause were simply about the intent of a fork of some original library, it would be almost completely ineffective, because when people fork libraries and copy them into their projects they generally intend to do so; that doesn't mean that Debian wants to support that.
The point of that policy exception was to avoid outlawing things like Gnulib (https://www.gnu.org/software/gnulib/), which is specifically designed from the start to be copied into projects at the source level (and comes with various tools to make that more maintainable). It's a very different kind of thing.
Even then, more recently there's been a movement to regenerate Gnulib files in packages that use it from the gnulib package in Debian.
vkroots - because the creator of a project intends it to be used via embedding (but it's already packaged with specific commit needed by gamescope, so it's fine for now)
I'm not quite sure from looking at https://github.com/misyltoad/vkroots, but that may be OK. If it's easy to use the packaged version, that's better.
-- Colin Watson (he/him) [cjwat...@debian.org]
