all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Trev <trev@trevdev.ca>
To: guix-devel@gnu.org
Subject: Stumpwm Contrib Packages
Date: Sun, 11 Sep 2022 08:02:31 -0700	[thread overview]
Message-ID: <87o7vmlzso.fsf@codinator.mail-host-address-is-not-set> (raw)


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


             reply	other threads:[~2022-09-17 12:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 15:02 Trev [this message]
2022-09-17 12:28 ` Stumpwm Contrib Packages Antonio Carlos Padoan Junior
2022-09-17 12:53 ` Maxime Devos
2022-10-04 21:50   ` John Kehayias
  -- strict thread matches above, loose matches on Subject: below --
2022-09-18 16:11 jgart
2022-09-18 16:32 ` Trev
2022-09-18 17:14   ` jgart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7vmlzso.fsf@codinator.mail-host-address-is-not-set \
    --to=trev@trevdev.ca \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.