GrizzlT

Could you write a detailed explanation of the steps you went through to get that behavior? It'll be easier for others to help if they have a way of recreating...

What version of velocity are you using?

@TheMysterys Could you show us your full log? (preferably something that's readable like pastebin)

Great feedback, I'll make changes accordingly! @spikespaz should I change `final` and `prev` in this PR as well? Or is that up for discussion some other day?

@spikespaz Are you sure you're looking at the changes of all commits combined? My force-pushed commits should already contain all the changes requested. This looks like something from git(hub) on...

> `callPackage` itself can be overridden (though unlikely), for example if cross-compiling. As mentioned in my review, it is inadvisable to be using `prev.callPackage`. It looks like `self` and `super`...

I am playing around with a new solution to this problem right now. I find it a limitation that dependencies of the final output package should be exposed to the...

> If the user desires to _not_ have shadowed package attributes in their `pkgs`, they may always use the flake's `packages.${system}` attributes. True, although this has the cost of an...

> > you end up missing out on a bunch of binary cache speedup. > > Using overlays, you knowlingly give this up. > Can you please elaborate? What do...

@spikespaz This PR is also ready for merge last I checked, I only changed the overlay to use `final` over `prev` everywhere. I also changed the name of `wlroots` in...