Github messages for voidlinux
 help / color / mirror / Atom feed
From: wael444 <wael444@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: nvidia-open
Date: Sat, 09 Jul 2022 12:43:33 +0200	[thread overview]
Message-ID: <20220709104333.9Cx91HG0m3oG3ga2tZHcv3L0_Q_FWgmxyN4inagk6yU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37123@inbox.vuxu.org>

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

New comment by wael444 on void-packages repository

https://github.com/void-linux/void-packages/issues/37123#issuecomment-1179521963

Comment:
the way `xbps-src` works is it is built in a chroot or a different system from the host system.
doing this is impossible,

kiss(1) and makepkg(1) both use the host system as the builder.

  parent reply	other threads:[~2022-07-09 10:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14  7:31 [ISSUE] " nvidiaLinuxUser4
2022-05-17  4:04 ` hervyqa
2022-05-22 13:54 ` nvidiaLinuxUser
2022-05-22 19:38 ` mvf
2022-05-22 19:39 ` mvf
2022-05-31 17:20 ` nvidiaLinuxUser
2022-05-31 17:21 ` nvidiaLinuxUser
2022-05-31 18:26 ` abenson
2022-05-31 19:45 ` nvidiaLinuxUser
2022-05-31 23:34 ` abenson
2022-06-01  4:43 ` nvidiaLinuxUser
2022-06-01  5:04 ` nvidiaLinuxUser
2022-06-01  5:14 ` nvidiaLinuxUser
2022-06-01  5:21 ` nvidiaLinuxUser
2022-06-01  5:59 ` nvidiaLinuxUser
2022-07-02 18:20 ` nvidiaLinuxUser
2022-07-02 18:20 ` nvidiaLinuxUser
2022-07-09  9:31 ` wael444
2022-07-09 10:42 ` nvidiaLinuxUser
2022-07-09 10:43 ` wael444 [this message]
2022-07-09 11:36 ` paper42
2022-07-10  4:28 ` wael444
2022-07-10  5:22 ` wael444
2022-07-10  5:37 ` wael444
2022-07-10  5:37 ` wael444
2022-12-10 12:25 ` nvidiaLinuxUser
2022-12-10 12:25 ` [ISSUE] [CLOSED] " nvidiaLinuxUser
2022-12-10 12:26 ` nvidiaLinuxUser
2022-12-10 12:33 ` wael444

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=20220709104333.9Cx91HG0m3oG3ga2tZHcv3L0_Q_FWgmxyN4inagk6yU@z \
    --to=wael444@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).