Hey Guix,
I am trying to decide whether or not to contribute a refactor of stumpwm-contrib in gnu/packages/wm.scm. It feels like each contrib module should be its own package with its own checkout and that it might be a bad idea to update all of the contrib modules through one common ancestor. If you are not familar with stumpwm and stumpwm-contrib, you can see the source repository here: https://github.com/stumpwm/stumpwm-contrib The inheritance I am referring to is here: https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/wm.scm#n1942 My reasoning for this is that if breaking changes are introduced to one module, but wanted updates happen to another, it would be nice to avoid the breaking changes and get the updates. I have some related contributions to stumpwm-contrib that I would like to submit but I would rather wait and see what others may think first and perhaps avoid making the effort to refactor where the effort is not wanted. If I run into personal issues with the current pattern, I can always just "fork" a module into my own channel, after all. -- Trev : 0FB7 D06B 4A2A F07E AD5B 1169 183B 6306 8AA1 D206
