From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37401@debbugs.gnu.org
Subject: [bug#37401] [PATCH 2/2] pack: Add packages in the order in which they appear on the command line.
Date: Wed, 18 Sep 2019 18:27:42 +0200 [thread overview]
Message-ID: <CAJ3okZ3yYVPMEVazbMRnwH_QhOCuigDw6Ygh3K3fRxAxQG4hhw@mail.gmail.com> (raw)
In-Reply-To: <87zhj75i4w.fsf@gnu.org>
Hi,
That really nice!
Thank you.
On Sat, 14 Sep 2019 at 11:43, Ludovic Courtès <ludo@gnu.org> wrote:
> It’s mostly so that if you do ‘guix pack -f docker sed grep findutils’
> the repo name is “sed-grep-findutils” and not “findutils-grep-sed”.
It is not in the doc, right?
If I want to create a "profile" with a meaningful name, then the order
after '-f' becomes important. Maybe one line explaining, something
like:
(current doc)
The result is a tarball that can be passed to the ‘docker load’ command.
See the Docker documentation
(https://docs.docker.com/engine/reference/commandline/load/) for more
information.
(addition)
Note that the profile name is built using the package names.
Well, and what happens if there is 10 or more packages? Is the name trimmed?
All the best,
simon
next prev parent reply other threads:[~2019-09-18 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 15:43 [bug#37401] [PATCH 0/2] 'guix pack -f docker' uses a meaningful "repository name" Ludovic Courtès
2019-09-13 15:51 ` [bug#37401] [PATCH 1/2] pack: Provide a meaningful "repository name" for Docker Ludovic Courtès
2019-09-13 15:51 ` [bug#37401] [PATCH 2/2] pack: Add packages in the order in which they appear on the command line Ludovic Courtès
2019-09-13 16:16 ` Ricardo Wurmus
2019-09-14 9:42 ` Ludovic Courtès
2019-09-18 16:27 ` zimoun [this message]
2019-09-18 20:48 ` Ludovic Courtès
2019-09-13 16:18 ` [bug#37401] [PATCH 1/2] pack: Provide a meaningful "repository name" for Docker Ricardo Wurmus
2019-09-14 9:45 ` Ludovic Courtès
2019-09-16 8:59 ` bug#37401: " Ludovic Courtès
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=CAJ3okZ3yYVPMEVazbMRnwH_QhOCuigDw6Ygh3K3fRxAxQG4hhw@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=37401@debbugs.gnu.org \
--cc=ludo@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.