unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 37401@debbugs.gnu.org
Subject: [bug#37401] [PATCH 0/2] 'guix pack -f docker' uses a meaningful "repository name"
Date: Fri, 13 Sep 2019 17:43:26 +0200	[thread overview]
Message-ID: <20190913154326.19020-1-ludo@gnu.org> (raw)

Hello!

This changes ‘guix pack -f docker’ so that the “repository name”
that shows up in the output of ‘docker images’ is more meaningful
than just “profile”, as it was until now (I think it was zimoun
who initially reported that this could be improved. :-)).

Namely, that name is now constructed using the names of the packages
available in the pack.

Thoughts?

Thanks,
Ludo’.

Ludovic Courtès (2):
  pack: Provide a meaningful "repository name" for Docker.
  pack: Add packages in the order in which they appear on the command
    line.

 guix/docker.scm       | 43 ++++++++++++++++++++++++++++++-------------
 guix/scripts/pack.scm | 16 +++++++++++++++-
 2 files changed, 45 insertions(+), 14 deletions(-)

-- 
2.23.0

             reply	other threads:[~2019-09-13 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-13 15:43 Ludovic Courtès [this message]
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
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

  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=20190913154326.19020-1-ludo@gnu.org \
    --to=ludo@gnu.org \
    --cc=37401@debbugs.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 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).