all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 42289@debbugs.gnu.org
Subject: bug#42289: recursive import does not dort alphabetically
Date: Tue, 08 Mar 2022 10:19:01 +0100	[thread overview]
Message-ID: <87r17c4xa2.fsf@gmail.com> (raw)
In-Reply-To: <e71b3b30-c81a-bc64-d7e9-409d588ebde6@crazy-compilers.com> (Hartmut Goebel's message of "Thu, 9 Jul 2020 09:53:05 +0200")

Hi Hartmut,

On jeu., 09 juil. 2020 at 09:53, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:
> In most gnu/packages/*.scm files are (expected to be) sorted alphabetically.

While I agree with this recommendation to sort alphabetically
gnu/packages/*.scm...

> Now when importing some packages recursivly, packages are output in
> order of the dependency graph, thus authors need to sort them manually.

...I think it is not a good idea to sort alphabetically the output of
the importers, because:

 1. the packages have to be added dependency-sorted,
 2. since each imported package is not alphabetically adjacent in the
 larger collection of already available packages, the user still needs
 to find the correct location.

Therefore, I am in favor to close this issue as wontfix notabug.  WDYT?


Cheers,
simon




      parent reply	other threads:[~2022-03-08 10:23 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
2020-07-16 11:41           ` Julien Lepiller
2020-07-16 18:23         ` Leo Famulari
2022-03-08  9:19 ` zimoun [this message]

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=87r17c4xa2.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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 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.