From: endigma <endigma@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: update docker
Date: Wed, 21 Apr 2021 02:17:25 +0200 [thread overview]
Message-ID: <20210421001725.IK4zr0faPkdYk-Pteqx-0vpTVR7qNFtAWF7iRBkpqtA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30244@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
New comment by endigma on void-packages repository
https://github.com/void-linux/void-packages/pull/30244#issuecomment-823683741
Comment:
> > Actually... I looking at [9b3c344](https://github.com/void-linux/void-packages/commit/9b3c344a79a1930062ec7a0df22882f3a04127ec) again, it seems that docker was just renamed to docker-cli, and that it doesn't actually have any other docker- package... why was it split?
>
> I mean³: I understand there might be a benefit to splitting **moby** out of **docker**, but why rename **docker** to **docker-cli** instead of just adding **moby** as a dependency to **docker**? Is it even possible to use **docker-cli** without **moby**?
The `docker` package isn't a rename of docker-cli, it's a effectively a metapackage that pulls in `docker-cli`, `moby`, `tini`. This was done because these tools are not codependent, moby can function without docker-cli as docker-cli can function without moby.
next prev parent reply other threads:[~2021-04-21 0:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 22:56 [PR PATCH] " radiden
2021-04-20 17:22 ` [PR PATCH] [Closed]: " radiden
2021-04-20 17:22 ` [PR PATCH] [Updated] " radiden
2021-04-20 17:39 ` radiden
2021-04-20 18:23 ` radiden
2021-04-20 18:52 ` pudiva
2021-04-20 19:09 ` pudiva
2021-04-20 19:10 ` pudiva
2021-04-20 19:43 ` ahesford
2021-04-20 21:39 ` endigma
2021-04-20 22:53 ` pudiva
2021-04-20 23:02 ` pudiva
2021-04-20 23:06 ` ahesford
2021-04-20 23:10 ` pudiva
2021-04-21 0:16 ` endigma
2021-04-21 0:17 ` endigma [this message]
2021-04-22 20:13 ` endigma
2021-05-03 18:38 ` Skaytacium
2021-05-03 18:41 ` Skaytacium
2021-05-03 18:45 ` [PR PATCH] [Merged]: " ahesford
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=20210421001725.IK4zr0faPkdYk-Pteqx-0vpTVR7qNFtAWF7iRBkpqtA@z \
--to=endigma@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).