unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org
Subject: Re: Multiple sources
Date: Thu, 22 Jul 2021 19:07:56 +0200	[thread overview]
Message-ID: <20210722190756.263cb40e@tachikoma.lepiller.eu> (raw)
In-Reply-To: <K45SHG4YwrzKhJga-a_hdURoAH4wHVfhSrTTYOGwFqi0n1QL0-toABKEZHHbwIxzVaHs3-zT6ro_g-DYXSR1hb4s99RYgay716hMitbDNcs=@protonmail.com>

Le Thu, 22 Jul 2021 16:49:14 +0000,
phodina via <help-guix@gnu.org> a écrit :

> Dear all,
> is there a way to specify multiple sources for building a package? Or
> do I have to create for each source a package (use copy-build-system)
> and then use it as a input for the final package with custom phases?
> 
> Let me give you an example. I have a git repo with source code to
> build and then another with some scripts to run and modify the first
> one. Also the second repo is not applicable as set of patches and it
> can't be merged into the first one.
> 
> Kind regards
> Petr

Maybe you can use the first repo as the source, and use the second as
an input, then have a phase to copy the files in place?

You can do something like this in the inputs:

(inputs
 `(("second-repo" ,(origin
                     (method url-fetch)
                     (uri ...)
                     ...))))

and in a phase you could do something like

(with-directory-excursion "some-place"
  (invoke "tar" "xf" (assoc-ref inputs "second-repo")))

(or copy if it's not a tar)

HTH!


  reply	other threads:[~2021-07-22 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 16:49 Multiple sources phodina via
2021-07-22 17:07 ` Julien Lepiller [this message]
2021-07-22 18:03   ` phodina

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=20210722190756.263cb40e@tachikoma.lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.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).