all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jesse Gibbons <jgibbons2357@gmail.com>
To: ison@airmail.cc
Cc: help-guix@gnu.org
Subject: Re: When is it appropriate to rename a file?
Date: Mon, 17 Jun 2019 11:18:53 -0600	[thread overview]
Message-ID: <20190617111853.34a5d613@gmail.com> (raw)

>Date: Sun, 16 Jun 2019 12:21:47 -0600
>From: ison <ison@airmail.cc>
>To: Jesse Gibbons <jgibbons2357@gmail.com>
>Cc: help-guix@gnu.org
>Subject: Re: When is it appropriate to rename a file?
>Message-ID: <20190616182146.asihmoclm4yghh6p@cf0>
>Content-Type: text/plain; charset=us-ascii
>
>I'm not by any means the one who should be answering this question, but
>just wanted to throw the idea out there that perhaps such things are
>best saved for major version changes.
>Because it would require every user to rethink the modules they're
>using in their system config.scm
Look at some of these examples: guile-wm jrnl musl sl wv
How many users would put these in their config.scm?
>(and possibly packages that aren't installed with "system" would have
>to be re-installed manually).
I have a package and moved it to a different module. I haven't needed
to reinstall manually, and I upgraded it with a simple call to "guix
upgrade". 
>So perhaps on Guix 2.0, 3.0, etc. is when it would be acceptable to do
>house cleaning like renaming modules.
Major changes that break over 1200 packages are pushed every 2.5 months
or so according to the manual. Why should module refactoring be pushed
more rarely?

After much thought, I think I will make a new module for a new category
of package when the need arises and leave module cleanup to the
maintainers.

             reply	other threads:[~2019-06-17 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 17:18 Jesse Gibbons [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-16  3:43 When is it appropriate to rename a file? Jesse Gibbons
2019-06-16 18:21 ` ison

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=20190617111853.34a5d613@gmail.com \
    --to=jgibbons2357@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=ison@airmail.cc \
    /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.