Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: pacman-5.2.2
Date: Tue, 07 Jul 2020 17:39:17 +0200	[thread overview]
Message-ID: <20200707153917.ARM2rAfcSXd0dvcsfpYjUUqvvC2_xZmtsKwkS5tkAOM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22253@inbox.vuxu.org>

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

New review comment by sgn on void-packages repository

https://github.com/void-linux/void-packages/pull/22253#discussion_r450960191

Comment:
I'm sorry in advance if this sounds arguative.
I think `arch-install-scripts` could be downloaded to some unnamed directories.
From there, we can bootstrap a new ArchLinux chroot.

I've never used `arch-install-scripts` but I've used `debootstrap` (for some definition of use) and I think it's not necessary to be installed system-wide.

Based on that, I think I wasn't wrong to discourage `arch-install-scripts`

  parent reply	other threads:[~2020-07-07 15:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 10:13 [PR PATCH] New package: pacman-5.2.1 Oreo639
2020-05-24 10:23 ` [PR PATCH] [Updated] " Oreo639
2020-05-24 11:59 ` Oreo639
2020-05-24 23:02 ` Oreo639
2020-05-24 23:14 ` Oreo639
2020-05-24 23:16 ` Oreo639
2020-05-24 23:52 ` Oreo639
2020-05-24 23:54 ` Oreo639
2020-05-25  0:02 ` Oreo639
2020-05-26  0:48 ` Oreo639
2020-07-06 23:37 ` [PR PATCH] [Closed]: New package: pacman-5.2.2 sgn
2020-07-07 14:03 ` [PR REVIEW] " eli-schwartz
2020-07-07 14:05 ` eli-schwartz
2020-07-07 15:10 ` sgn
2020-07-07 15:13 ` sgn
2020-07-07 15:25 ` eli-schwartz
2020-07-07 15:37 ` eli-schwartz
2020-07-07 15:39 ` sgn [this message]
2020-07-07 15:46 ` eli-schwartz

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=20200707153917.ARM2rAfcSXd0dvcsfpYjUUqvvC2_xZmtsKwkS5tkAOM@z \
    --to=sgn@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).