mbox series

[bug#76910,v2,0/4] Add Hyprland Plugins (Update)

Message ID cover.1743237168.git.wongandj@icloud.com
Headers
Series Add Hyprland Plugins (Update) |

Message

Andrew Wong March 29, 2025, 8:32 a.m. UTC 
  This new version updates hyprscroller and hy3 to be compatible with the latest 0.48.0 release of Hyprland.

Andrew Wong (4):
  gnu: Add Hyprland plugins.
  gnu: Add hyprscroller.
  gnu: Add hy3.
  gnu: Add hypr-darkwindow.

 gnu/packages/wm.scm | 209 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 209 insertions(+)


base-commit: ce086e31f0f5c78be76fd228dfd7718ff6df584e

Comments

Gabriel Santos March 29, 2025, 12:06 p.m. UTC | #1 
Nice patch!

Would it be ok if I added hypr-dynamic-cursors[1] to it by
sending a V3?

[1] <https://github.com/VirtCode/hypr-dynamic-cursors>
Andrew Wong March 29, 2025, 2:16 p.m. UTC | #2 
On 3/29/25 8:06a, Gabriel Santos wrote> Would it be ok if I added 
hypr-dynamic-cursors[1] to it by
> sending a V3?
Sure, go ahead! While you're at it, could you add both of our names and 
addresses to the copyright at the top of the file? I keep forgetting to 
do it :p

On 3/29/25 9:58a, Gabriel Santos wrote:
> The policy for Guix is one package per commit.
> 
> Even with the use of a helper like hyprland-plugin,
> wouldn't that also apply here?

I thought about it, but I have submitted similar patches in the past[1] 
without any hangups, so I did the same here for the sake of simplicity.

> If you allow me to submit a v3, I think I could do that.

Sure, go ahead. I'm not attached to any particular commit arrangement.

On 3/29/25 9:51a, Gabriel Santos wrote:
> I noticed that the Flake for this plugin and for
> hypr-dynamic-cursors prefix the compiled file with
> "lib"[1, 2].
> 
> Do you know why that is? Would it also be necessary
> for Guix?

I'm not sure why. It's not a requirement for the plugins to work, so I'd 
guess it's just a convention of Nix or the packager.

[1] a9a13ebccc (gnu: Add libretro-beetle-psx., 2025-01-04)
Gabriel Santos March 29, 2025, 3:06 p.m. UTC | #3 
>Sure, go ahead! While you're at it, could you add both of our names and addresses to the copyright at the top of the file? I keep forgetting to do it :p

I wonder if the function for that could be loaded with
.dir-locals.el, but it probably has existed for a long
time, so maybe someone already tried that.

>I thought about it, but I have submitted similar patches in the past[1] without any hangups, so I did the same here for the sake of simplicity.

>Sure, go ahead. I'm not attached to any particular commit arrangement.

If there's no issues, I think it would be best to leave
it that way.