From: erezgeva <erezgeva@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Docker environment to build and test new packages
Date: Thu, 31 Mar 2022 17:36:42 +0200 [thread overview]
Message-ID: <20220331153642.ncZfiIBixAza2oUu8YxKwCCs1qQWNrsB4Aj6Z0nF7Cg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35410@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1084757177
Comment:
I do not want to build on the host system.
Docker container are the best clean and reproducible environments there is.
The link you send looks interesting.
It run
https://github.com/void-linux/void-packages/blob/master/common/travis/build.sh
It does not seems to have options to disable unshare or uchroot.
But looks like something in the environment is different.
Is it possible to use this Docker?
next prev parent reply other threads:[~2022-03-31 15:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 18:02 [ISSUE] " erezgeva
2022-02-04 18:07 ` Chocimier
2022-03-26 18:23 ` [ISSUE] [CLOSED] " Chocimier
2022-03-29 1:53 ` erezgeva
2022-03-29 2:06 ` Duncaen
2022-03-29 9:13 ` erezgeva
2022-03-29 12:33 ` erezgeva
2022-03-29 17:40 ` Chocimier
2022-03-31 13:25 ` erezgeva
2022-03-31 13:28 ` erezgeva
2022-03-31 14:27 ` Duncaen
2022-03-31 15:36 ` erezgeva [this message]
2022-03-31 19:47 ` Anachron
2022-03-31 21:44 ` erezgeva
2022-03-31 22:50 ` paper42
2022-04-01 4:31 ` Anachron
2022-04-01 4:38 ` Anachron
2022-04-01 8:07 ` erezgeva
2022-04-01 10:09 ` Duncaen
2022-04-01 10:55 ` Anachron
2023-04-27 10:26 ` bruceloco
2023-04-27 11:21 ` classabbyamp
2023-04-27 13:11 ` bruceloco
2023-04-27 13:45 ` bruceloco
2023-04-27 18:49 ` bruceloco
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=20220331153642.ncZfiIBixAza2oUu8YxKwCCs1qQWNrsB4Aj6Z0nF7Cg@z \
--to=erezgeva@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).