* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
@ 2021-10-27 21:22 ` Chocimier
2021-10-27 21:40 ` Chocimier
` (15 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Chocimier @ 2021-10-27 21:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-953322268
Comment:
Do we need it? (lib)curl is already part of stage2 base-devel, and stage0 base-devel isn't used for anything but producing stage1.
https://github.com/void-linux/void-packages/runs/4021578772?check_suite_focus=true#step:3:35
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
2021-10-27 21:22 ` Chocimier
@ 2021-10-27 21:40 ` Chocimier
2021-10-28 1:30 ` q66
` (14 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Chocimier @ 2021-10-27 21:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-953322268
Comment:
Do we need it? (lib)curl is already part of stage2 base-chroot, and stage0 base-chroot isn't used for anything but producing stage1.
https://github.com/void-linux/void-packages/runs/4021578772?check_suite_focus=true#step:3:35
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
2021-10-27 21:22 ` Chocimier
2021-10-27 21:40 ` Chocimier
@ 2021-10-28 1:30 ` q66
2021-10-28 4:29 ` the-maldridge
` (13 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: q66 @ 2021-10-28 1:30 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 233 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-953428533
Comment:
i'd sooner be in favor of removing network access from the chroot than further depending on it
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (2 preceding siblings ...)
2021-10-28 1:30 ` q66
@ 2021-10-28 4:29 ` the-maldridge
2021-10-28 12:25 ` q66
` (12 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: the-maldridge @ 2021-10-28 4:29 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
New comment by the-maldridge on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-953492982
Comment:
@Chocimier I want the binary in the ethereal masterdir, I can just add it there, but I'm not sure if there's a problem with doing that if it will cause curl to be picked up in places it shouldn't be.
@q66 I encourage you to try. I don't care about calling curl from inside of xbps-src's managed chroots, I only care about having the binary available.
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (3 preceding siblings ...)
2021-10-28 4:29 ` the-maldridge
@ 2021-10-28 12:25 ` q66
2021-10-29 0:52 ` ericonr
` (11 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: q66 @ 2021-10-28 12:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 216 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-953794981
Comment:
if you don't care about calling it, why have it available in the first place?
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (4 preceding siblings ...)
2021-10-28 12:25 ` q66
@ 2021-10-29 0:52 ` ericonr
2021-10-29 15:49 ` Chocimier
` (10 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: ericonr @ 2021-10-29 0:52 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-954326348
Comment:
Purpose of `chroot-curl` afaiu is to perform maintenance tasks *after* `xbps-src` has done its thing.
A smaller package is easier to build / maintain (could depend only on OpenSSL), and it would always be available, but without a library and with a different executable name to avoid any silliness in configure scripts from picking it up.
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (5 preceding siblings ...)
2021-10-29 0:52 ` ericonr
@ 2021-10-29 15:49 ` Chocimier
2021-10-29 15:50 ` Chocimier
` (9 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Chocimier @ 2021-10-29 15:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-954848520
Comment:
What @ericonr proposes looks fine, but it's discussion on solution when problem wasn't stated.
Requested bikeshedding: why not to install curl after xbps-src is done?
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (6 preceding siblings ...)
2021-10-29 15:49 ` Chocimier
@ 2021-10-29 15:50 ` Chocimier
2021-10-29 15:51 ` the-maldridge
` (8 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: Chocimier @ 2021-10-29 15:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 324 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-954848520
Comment:
What @ericonr proposes looks fine, but it's discussion on solution when problem wasn't stated.
Requested bikeshedding: why not to install [regular] curl after xbps-src is done?
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (7 preceding siblings ...)
2021-10-29 15:50 ` Chocimier
@ 2021-10-29 15:51 ` the-maldridge
2021-10-29 17:39 ` ericonr
` (7 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: the-maldridge @ 2021-10-29 15:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
New comment by the-maldridge on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-954850066
Comment:
@Chocimier the use case is to POST package files and logs back after builds complete. In this case installing curl after xbps-src is done would result in it being installed for every build, which while a relatively trivial load on the internal mirror would be slow and inefficient over using a pre-cached filesystem image that already includes curl.
This could also be done as a package that is not depended on by anything and gets added to the ethereal masterdir during a build step to keep it out of local chroots and environments where its presence is not required.
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (8 preceding siblings ...)
2021-10-29 15:51 ` the-maldridge
@ 2021-10-29 17:39 ` ericonr
2021-10-30 1:33 ` sgn
` (6 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: ericonr @ 2021-10-29 17:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 337 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-954923677
Comment:
I think the most important detail here is for bootstrapping builders. You can't install `curl` afterwards if it hasn't been built yet, but it works if `chroot-curl` is part of the bootstrap set.
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (9 preceding siblings ...)
2021-10-29 17:39 ` ericonr
@ 2021-10-30 1:33 ` sgn
2021-10-30 1:34 ` sgn
` (5 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: sgn @ 2021-10-30 1:33 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-955122826
Comment:
> IYou can't install `curl` afterwards if it hasn't been built yet
libcurl is in stage 2 chroot, so it's built definitely.
If we want to provide it in builders, we can put current `curl` binary somewhere not in `$PATH`?
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (10 preceding siblings ...)
2021-10-30 1:33 ` sgn
@ 2021-10-30 1:34 ` sgn
2021-10-30 4:11 ` q66
` (4 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: sgn @ 2021-10-30 1:34 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-955122987
Comment:
Anyway, I notice license is distributed with `curl` package instead of `libcurl` package. So, we're doing copyright infringement by distribute `libcurl` without the copyright notice and condition?
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (11 preceding siblings ...)
2021-10-30 1:34 ` sgn
@ 2021-10-30 4:11 ` q66
2021-10-30 6:19 ` sgn
` (3 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: q66 @ 2021-10-30 4:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-955142336
Comment:
not particularly, arguably it's not required to ship the license files at all (e.g. Alpine does not ship them, with the claim being that the SPDX tags are enough)
but even then, the distribution of the software includes all subpackages, it should not be necessary to include the license in all of them
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (12 preceding siblings ...)
2021-10-30 4:11 ` q66
@ 2021-10-30 6:19 ` sgn
2021-11-04 11:09 ` ericonr
` (2 subsequent siblings)
16 siblings, 0 replies; 18+ messages in thread
From: sgn @ 2021-10-30 6:19 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 392 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-955157787
Comment:
> but even then, the distribution of the software includes all subpackages, it should not be necessary to include the license in all of them
I'm not advocate to include the license in all of them, but ship the license with libcurl instead of curl
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] chroot-curl
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (13 preceding siblings ...)
2021-10-30 6:19 ` sgn
@ 2021-11-04 11:09 ` ericonr
2022-06-10 2:13 ` [BIKESHED] curl license file location github-actions
2022-06-24 2:15 ` [ISSUE] [CLOSED] " github-actions
16 siblings, 0 replies; 18+ messages in thread
From: ericonr @ 2021-11-04 11:09 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-960656720
Comment:
> I'm not advocate to include the license in all of them, but ship the license with libcurl instead of curl
I think that's reasonable.
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [BIKESHED] curl license file location
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (14 preceding siblings ...)
2021-11-04 11:09 ` ericonr
@ 2022-06-10 2:13 ` github-actions
2022-06-24 2:15 ` [ISSUE] [CLOSED] " github-actions
16 siblings, 0 replies; 18+ messages in thread
From: github-actions @ 2022-06-10 2:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/33781#issuecomment-1151841426
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 18+ messages in thread* Re: [ISSUE] [CLOSED] [BIKESHED] curl license file location
2021-10-27 5:24 [ISSUE] [BIKESHED] chroot-curl the-maldridge
` (15 preceding siblings ...)
2022-06-10 2:13 ` [BIKESHED] curl license file location github-actions
@ 2022-06-24 2:15 ` github-actions
16 siblings, 0 replies; 18+ messages in thread
From: github-actions @ 2022-06-24 2:15 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
Closed issue by the-maldridge on void-packages repository
https://github.com/void-linux/void-packages/issues/33781
Description:
In re-imagining what build infrastructure around xbps-src looks like, having the ability to run lots of things inside the ethereal chroot becomes appealing. Everything I've wanted to do so far has worked, but for doing an HTTP post of files it would be ideal to have curl in the chroot. Thoughts on adding a `chroot-curl` ?
^ permalink raw reply [flat|nested] 18+ messages in thread