Why include hypr- in Void, but not Hyprland?

[G00d-Syst3m]

Why does Void Linux include packages like https://voidlinux.org/packages/?arch=x86_64&q=hypr in its repository, but reject requests to package Hyprland (as seen in https://github.com/void-linux/void-packages/issues?q=is%3Aissue%20hyprland)?

[dogknowsnx]

... but reject requests ...

Counterquestion: Would you be more inclined to do anything the more you already said "no"?

I cannot speak for Void members (that do the actual merging), but it is basically the same as with any package.

It depends on whether a member is/isn't interested, while taking into consideration stability, maintanance (burden), or simply a "need" for a specific package.

Can the WM you mentioned be considered stable? (I don't know). Is there a particular need for it? No. Void's repo contains plenty of WMs/DEs to choose from. Then there's the part of maintaining a package, and quite a few of them will be abandoned at some point, probably especially those that got "hyped" until the next thing comes along.

Last but not least (while not directly answering your question), something not being readily packaged isn't (necessarily) preventing anybody from installing it on Void Linux -EDIT- or from picking a different distro with a differently sorted repo, for that matter.

(I'm basically writing this as a /dev/null so that those doing the actual work don't have to - not that they do)

[ahesford]

We won't package hyprland because there are substantial technical issues with hyprland that we do not wish to accommodate. These have been described ad nauseam elsewhere and will not be restated here. The other tools do not suffer from these problems.