Hi,
Thanks for the heads up. I am still working on structuring all this
properly.
So far, this is what I have:
https://salsa.debian.org/NyxTrail/hyprland
Regarding the sub-packages, udis86 seems to be based on a fork of
another project of the same name:
https://github.com/canihavesomecoffee/udis86 (hyprland depends on this one)
https://github.com/vmt/udis86 (this one is the original project)
There does not seem to be any official releases upstream (udis86) for
the commit Hyprland depends on (commit: 5336633). In fact, their
(udis86) latest release seems to be v1.7.2, on Sep 2 2013.
Considering how Hyprland likes to declare their dependencies based on
non-release commits, I do not think we can depend on any release
versions of these packages.
I have successfully moved libwlroots.so.* to a "private" directory under
/usr/lib/hyprland and updated the RPATH on the Hyprland binary to
reflect that. This seems to work fine so far.
It might be possible to exclude tracy (may be even remove it?), but I
haven't explored this yet. In this case, the commit Hyprland references
does have a release version. But, may be we should not depend on that?
Finally, the build output for hyprland-protocols are a few header files.
So far I have been trying to include these in a 'hyprland-dev' package
along with everything else under the 'installheaders' Make target.
If required, I think it should be trivial to move these headers to a
hyprland-protocols-dev package.`
As I mentioned before, the source tarball from Hyprland includes the
source for all these submodules.
Perhaps these modules should be considered a part of Hyprland itself
since they are included verbatim in the source package? They also do not
seem to generate any binaries (or other artifacts) that might pollute
the rest of the system.
Let me know if you have any thoughts/feedback. This is my first time
building a package :)
Thanks,
Alan (NyxTrail)
