Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: docker-buildx-0.7.1
Date: Sun, 20 Feb 2022 12:54:03 +0100	[thread overview]
Message-ID: <20220220115403.xxFfgdaFlDcRyoGEf2IeshJS1QGm2YbTXdm04oB_lV4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35682@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]

There's a merged pull request on the void-packages repository

New package: docker-buildx-0.7.1
https://github.com/void-linux/void-packages/pull/35682

Description:
I had to use this command at work and it simply didn't exist. I had previously used it on Arch and didn't really know why it wasn't available on Void as well.

It happens that this command is a Docker CLI plugin, and comes bundled with Docker when distributed via DEBs or RPMs, but Arch also packages it along with their Docker package.

In my opinion, it makes more sense to package this just like Docker Compose (which since `v2` is also a Docker CLI plugin), that is, as a separate package, easy to install, and which will work out of the box once installed.

P.S.: I based this template off `docker-compose`'s.

#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
 
#### Local build testing
- [x] I built this PR locally for my native architecture, (x86_64, both for glibc and musl)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl


      parent reply	other threads:[~2022-02-20 11:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 14:53 [PR PATCH] " gbrlsnchs
2022-02-19 15:30 ` [PR REVIEW] " paper42
2022-02-19 15:30 ` paper42
2022-02-19 15:30 ` paper42
2022-02-19 15:30 ` paper42
2022-02-20  2:30 ` gbrlsnchs
2022-02-20  2:32 ` [PR PATCH] [Updated] " gbrlsnchs
2022-02-20  2:51 ` gbrlsnchs
2022-02-20  2:52 ` [PR REVIEW] " gbrlsnchs
2022-02-20  2:52 ` gbrlsnchs
2022-02-20  2:56 ` [PR PATCH] [Updated] " gbrlsnchs
2022-02-20  2:58 ` gbrlsnchs
2022-02-20 11:54 ` paper42 [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=20220220115403.xxFfgdaFlDcRyoGEf2IeshJS1QGm2YbTXdm04oB_lV4@z \
    --to=paper42@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).