all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Timothy Washington <twashing@gmail.com>
Cc: Kaelyn <kaelyn.alexi@protonmail.com>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	 Guix Devel <guix-devel@gnu.org>,
	Tobias Kortkamp <tobias.kortkamp@gmail.com>
Subject: Re: Howto reference a custom package from a manifest
Date: Tue, 23 May 2023 09:54:15 -0700	[thread overview]
Message-ID: <CAFHYt55hhVVO-M88=viqU-yXnzzLZLk=1E+0HGsEDOSC=4ho+g@mail.gmail.com> (raw)
In-Reply-To: <CAADtM-YjWSx3E86guq_djFDyZcqj7Ua0n5oScAwK41bXvL21iQ@mail.gmail.com>

Hi Timothy,

On Tue, May 23, 2023 at 12:31 AM Timothy Washington <twashing@gmail.com> wrote:
>
> Yes that was it! I added "(native-inputs (list perl python))" to my package definition.
>
> $ guix build -L ~/dotfiles/ rust-rustscan   # A. Now builds again!

Hats off to Tobias Kortkamp for pinpointing the issue so confidently
and so quickly! We have a lot of amazing packaging talent on this
list.

> i. Using a direct "guix build" gives you a directory in "/gnu/store". And you can add that bin to your PATH.

You may wish to have a look at 'guix shell'. It does something very
similar via an intermediate collection of symlinks that look like an
aggregate file tree, which we call a profile.

> I'm attaching the full package definition to this email.

Should 'rustscan' perhaps become part of Guix? I'd be happy to assist
with preparing such a patch while preserving your authorship.

Kind regards
Felix


  parent reply	other threads:[~2023-05-23 16:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  6:51 Howto reference a custom package from a manifest Timothy Washington
2023-05-19 16:15 ` Simon Tournier
     [not found]   ` <CAADtM-bc9FU6B+k5UaJctk3+T2aPO_z2edp=SM5LoZgd5JeNYA@mail.gmail.com>
2023-05-21 16:46     ` Simon Tournier
2023-05-21 20:35       ` Timothy Washington
2023-05-22  8:41         ` issue with packaging 'rustscan' Simon Tournier
2023-05-22  9:56           ` Tobias Kortkamp
2023-05-22 20:21             ` Timothy Washington
2023-05-22 18:17         ` Howto reference a custom package from a manifest Kaelyn
2023-05-22 20:20           ` Timothy Washington
2023-05-23 16:39             ` Kaelyn
2023-05-24 20:25               ` Timothy Washington
2023-05-24 22:16                 ` Kaelyn
2023-05-26 23:27                   ` Timothy Washington
2023-05-23 16:54             ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2023-05-24 20:10               ` Timothy Washington

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='CAFHYt55hhVVO-M88=viqU-yXnzzLZLk=1E+0HGsEDOSC=4ho+g@mail.gmail.com' \
    --to=guix-devel@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=kaelyn.alexi@protonmail.com \
    --cc=tobias.kortkamp@gmail.com \
    --cc=twashing@gmail.com \
    --cc=zimon.toutoune@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.