unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 42289@debbugs.gnu.org
Subject: bug#42289: recursive import does not dort alphabetically
Date: Thu, 9 Jul 2020 13:39:55 -0400	[thread overview]
Message-ID: <20200709173955.GA22616@jasmine.lan> (raw)
In-Reply-To: <87692d5d-0650-c2bd-1533-54b38677d97e@crazy-compilers.com>

On Thu, Jul 09, 2020 at 01:26:03PM +0200, Hartmut Goebel wrote:
> Most file I've been working on ask for sorting alphabetically. (And IMHO
> this is a good recommendation to follow.)

What are the benefits of sorting packages?

The ordering of packages is not usually important to the machine, and
humans can search for the package names.

I think that sorting the packages is not necessarily desired, especially
for modules where a lot of packages may be imported (e.g. Rust). It
makes the Git diffs harder to understand and work with when merging or
rebasing, compared to just adding the new packages at the end of the
file.

In cases where packages are inherited to create multiple package
versions, alphanumerical sorting breaks the inheritance [0], although
inheritance is problematic in its own right and we should probably stop
using it.

[0] See <https://lists.gnu.org/archive/html/guix-devel/2020-04/msg00040.html>




  parent reply	other threads:[~2020-07-09 17:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  7:53 bug#42289: recursive import does not dort alphabetically Hartmut Goebel
2020-07-09  9:36 ` zimoun
2020-07-09 11:26   ` Hartmut Goebel
2020-07-09 14:02     ` zimoun
2020-07-09 17:39     ` Leo Famulari [this message]
2020-07-15 19:10       ` Hartmut Goebel
2020-07-16 11:35         ` zimoun
2020-07-16 11:41           ` Julien Lepiller
2020-07-16 18:23         ` Leo Famulari
2022-03-08  9:19 ` zimoun

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20200709173955.GA22616@jasmine.lan \
    --to=leo@famulari.name \
    --cc=42289@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).