unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>,
	Leo Famulari <leo@famulari.name>
Cc: 42289@debbugs.gnu.org
Subject: bug#42289: recursive import does not dort alphabetically
Date: Thu, 16 Jul 2020 13:35:23 +0200	[thread overview]
Message-ID: <86wo33y9ok.fsf@gmail.com> (raw)
In-Reply-To: <a297d058-7973-9ba7-34e6-1341d0eeee2a@crazy-compilers.com>

Dear Hartmut,

On Wed, 15 Jul 2020 at 21:10, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote

> Many modules are sorted and some packages even contain a comment asking
> for being sorted. So I had the impression this is good practice.

I am not sure by the "many". :-)
Even gnu/packages/crate-io.scm which explicitly asks:

;;; Please: Try to add new module packages in alphabetic order.

and it is not really sorted. :-)

  cat crates-io.scm | grep 'define-public' | sort --check
  sort: -:6: disorder: (define-public rust-afl-0.5


> Also scanning through the file is easier for humans if packages are
> sorted - depends on personal work style.

It appears to me as a "good practise" too.  On the other hand,
personally I always scan the packages with "ag" (inside Emacs).


However, it is not the point since your initial request is about
alphabetical sort of "guix import"; which seems better than arbitrary
order (dependency order).  Whatever if gnu/packages/foo.scm is sorted or
not.

If "guix import" returns an alphanumerical sorted list, it is easier and
it does not bother the unsorted modules since the packages are new.

All the best,
simon




  reply	other threads:[~2020-07-16 11:36 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
2020-07-15 19:10       ` Hartmut Goebel
2020-07-16 11:35         ` zimoun [this message]
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=86wo33y9ok.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=42289@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=leo@famulari.name \
    /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).