Make it clear which version of awesome bling is compatible about bling HOT 5 CLOSED

Sorry, that it took so long. Should be alright now 😅

from bling.

It would be nice to include which version/commit bling is expected to work

from bling.

Hey, thanks for your issue! We want everything to be 4.3 compatible at least as long as 4.3 is the stable version. You are right, it seems like the request::wallpaper signal is not available in 4.3. Using that signal is a very clean solution though so maybe changing line 282 to the following would already be enough:

if awesome.version == "v4.3" then  
    awful.screen.connect_for_each_screen(set_wallpaper)
else
    screen.connect_signal("request::wallpaper", set_wallpaper)
end

@Grumph Before we start massacring your child, any thoughts on that?

from bling.

@SeraphyBR Honestly, the master branch of AwesomeWM should be safe to use. I do have an overlay for it that compiles AwesomeWM with features such as the playerctl GI and the upower GI.

final: prev: {
  awesome = (prev.awesome.overrideAttrs (old: rec {
    src = prev.fetchFromGitHub {
      owner = "awesomeWM";
      repo = "awesome";
      rev = "149d18e0e796b3a439b1d79c5ee0c93febfcdf69";
      sha256 = "02ahbph10sd5a4gv9wizcl0pmqd08mdc47w9bd28p5bldpk4vrvm";
    };
    GI_TYPELIB_PATH = "${prev.playerctl}/lib/girepository-1.0:"
      + "${prev.upower}/lib/girepository-1.0:" + old.GI_TYPELIB_PATH;
  })).override {
    stdenv = prev.clangStdenv;
    luaPackages = prev.lua52Packages;
    gtk3Support = true;
  };
}

If you use flakes, you can check out this repo where the flakes are automatically updated for those according packages.

But then again, bling does target the stable branch so this should be on the backlog for fixing.

from bling.

@Grumph Before we start massacring your child, any thoughts on that?

No problem for me, consider "my" child as this project's child, as long as it works for everyone who need it I'm happy :-D

from bling.