From: Joshua Branson <jbranso@dismail.de>
To: David Dashyan <mail@davie.li>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Bug? Importing (gnu rest ...) fails due to lack of patch files on build side.
Date: Fri, 16 Apr 2021 10:10:02 -0400 [thread overview]
Message-ID: <871rba722t.fsf@dismail.de> (raw)
In-Reply-To: <87blahltsn.fsf@davie.li> (David Dashyan's message of "Wed, 14 Apr 2021 01:10:48 +0300")
David Dashyan <mail@davie.li> writes:
I'm just responding so that you get a response. :)
Your last email had some pretty cool code bro! It certainly looks like
you're having fun with guix!
> Hello Guix!
>
> My update on this.
>
> So I though of a dirty hack...
>
> (define guix-patches
> (package
> (inherit guix)
> (name "guix-patches")
> (build-system copy-build-system)
> (arguments
> '(#:install-plan
> '(("gnu/packages/patches/"
> "share/guile/site/3.0/gnu/packages/patches/"))))
> (native-inputs '())
> (inputs '())
> (propagated-inputs '())
> (native-search-paths '())
> (home-page "")
> (synopsis "")
> (description "")
> (properties '())))
>
> The reasoning was that I can wrap everithing it in
> (with-extensions (list guix-patches ...) ...)
>
> But still loading patches fails. Even though they should be now in
> %load-path...
--
Joshua Branson (joshuaBPMan in #guix)
Sent from Emacs and Gnus
https://gnucode.me
https://video.hardlimit.com/accounts/joshua_branson/video-channels
https://propernaming.org
"You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar
next prev parent reply other threads:[~2021-04-16 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 9:48 Bug? Importing (gnu rest ...) fails due to lack of patch files on build side David Dashyan
2021-04-13 22:10 ` David Dashyan
2021-04-16 14:10 ` Joshua Branson [this message]
2021-04-17 21:39 ` David Dashyan
2021-04-25 16:24 ` Maxime Devos
2021-04-27 17:03 ` David Dashyan
2021-04-27 17:36 ` Maxime Devos
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=871rba722t.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
--cc=mail@davie.li \
/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).