all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37401@debbugs.gnu.org, "Ludovic Courtès" <ludovic.courtes@inria.fr>
Subject: [bug#37401] [PATCH 1/2] pack: Provide a meaningful "repository name" for Docker.
Date: Fri, 13 Sep 2019 18:18:23 +0200	[thread overview]
Message-ID: <87o8zoqieo.fsf@elephly.net> (raw)
In-Reply-To: <20190913155116.19225-1-ludo@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> From: Ludovic Courtès <ludovic.courtes@inria.fr>
>
> Previously, images produced by 'guix pack -f docker' would always show
> up as "profile" in the output of 'docker images'.  With this change,
> 'docker images' shows a name constructed from the packages found in the
> image--e.g., "bash-coreutils-grep-sed".

This looks good to me, thanks!

Just one thing to note: packages from other channels might have names
with characters outside of a-z.  All of those would show up as dots.

Also, a few package names include numbers, which are probably fine to
include.

--
Ricardo

  parent reply	other threads:[~2019-09-13 16:19 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
2019-09-18 20:48           ` Ludovic Courtès
2019-09-13 16:18   ` Ricardo Wurmus [this message]
2019-09-14  9:45     ` [bug#37401] [PATCH 1/2] pack: Provide a meaningful "repository name" for Docker 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=87o8zoqieo.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=37401@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    /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.