unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Olivier Dion via <help-guix@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>,
	Olivier Dion via <help-guix@gnu.org>, "(" <paren@disroot.org>,
	help-guix@gnu.org
Subject: Re: Guix as a native-inputs ?
Date: Wed, 03 Aug 2022 11:51:30 -0400	[thread overview]
Message-ID: <8735edwcjh.fsf@laura> (raw)
In-Reply-To: <17139594-8056-4955-BD84-24CF556BAC57@lepiller.eu>

On Tue, 02 Aug 2022, Julien Lepiller <julien@lepiller.eu> wrote:
> I suppose once you get information about these channels, you could
> create an inferior with these channels, and evaluate your package in
> it.

I think I will have to go with your proposal.  I already have the
packages defined in my channel.  It's just a matter of making a list of
them and adding it to the native-inputs instead of using Guix.  However,
this mean that I have to copy these packages when adding my package
to Guix channel.  It's not too much of a hassle.

-- 
Olivier Dion
oldiob.dev


  reply	other threads:[~2022-08-03 15:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 18:45 Guix as a native-inputs ? Olivier Dion via
2022-08-01 19:42 ` (
2022-08-02 13:41   ` Olivier Dion via
2022-08-02 13:44     ` (
2022-08-02 15:36       ` Olivier Dion via
2022-08-02 16:06         ` Julien Lepiller
2022-08-02 17:10           ` Olivier Dion via
2022-08-02 18:09             ` Julien Lepiller
2022-08-03 15:51               ` Olivier Dion via [this message]
2022-08-01 19:43 ` (
2022-08-01 20:34 ` Tobias Geerinckx-Rice
2022-08-01 22:05   ` Olivier Dion via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8735edwcjh.fsf@laura \
    --to=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=olivier.dion@polymtl.ca \
    --cc=paren@disroot.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 read-only IMAP folder(s) and NNTP newsgroup(s).