Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: chroot-curl-7.79.1
Date: Thu, 04 Nov 2021 02:19:01 +0100	[thread overview]
Message-ID: <20211104011901.eq7AWuHbrszh6mF3nSudbRbCZ0ODX5uT76IgGs043H8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33851@inbox.vuxu.org>

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

There is an updated pull request by ericonr against master on the void-packages repository

https://github.com/ericonr/void-packages chroot-curl
https://github.com/void-linux/void-packages/pull/33851

New package: chroot-curl-7.79.1
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/33851.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chroot-curl-33851.patch --]
[-- Type: text/x-diff, Size: 1312 bytes --]

From 8a6e3e88aeeef23cd25bfa124535778f6af9fa53 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Nogueira?= <erico.erc@gmail.com>
Date: Wed, 3 Nov 2021 22:16:03 -0300
Subject: [PATCH] chroot: create chroot-curl subpackage.

The new potential build infrastructure needs a curl binary to send build
results to outside the chroot, but we don't want it to be picked up by
build systems. libcurl is part of the masterdir environment already,
through binutils -> libdebuginfod -> libcurl, so we can simply copy the
binary with a different name, and have the package also depend on
libcurl.
---
 srcpkgs/chroot-curl   | 1 +
 srcpkgs/curl/template | 7 +++++++
 2 files changed, 8 insertions(+)
 create mode 120000 srcpkgs/chroot-curl

diff --git a/srcpkgs/chroot-curl b/srcpkgs/chroot-curl
new file mode 120000
index 000000000000..8b258ec33430
--- /dev/null
+++ b/srcpkgs/chroot-curl
@@ -0,0 +1 @@
+curl
\ No newline at end of file
diff --git a/srcpkgs/curl/template b/srcpkgs/curl/template
index 1ccf71d6d3d7..0d7ea1d62610 100644
--- a/srcpkgs/curl/template
+++ b/srcpkgs/curl/template
@@ -71,3 +71,10 @@ libcurl-devel_package() {
 		vmove usr/lib/pkgconfig
 	}
 }
+
+chroot-curl_package() {
+	short_desc+=" - for build infra use"
+	pkg_install() {
+		cp $DESTDIR/usr/bin/curl $PKGDESTDIR/usr/bin/chroot-curl
+	}
+}

  parent reply	other threads:[~2021-11-04  1:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31 18:50 [PR PATCH] " ericonr
2021-11-01  4:45 ` [PR REVIEW] " the-maldridge
2021-11-01  4:45 ` the-maldridge
2021-11-02  0:28 ` sgn
2021-11-02  0:42 ` ericonr
2021-11-02  0:42 ` ericonr
2021-11-02  0:42 ` ericonr
2021-11-04  1:04 ` ericonr
2021-11-04  1:19 ` ericonr [this message]
2021-11-04  1:23 ` [PR PATCH] [Updated] " ericonr
2021-11-04 11:07 ` [PR PATCH] [Merged]: " ericonr

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=20211104011901.eq7AWuHbrszh6mF3nSudbRbCZ0ODX5uT76IgGs043H8@z \
    --to=ericonr@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).