unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: phodina <phodina@protonmail.com>
To: help-guix@gnu.org
Cc: Julien Lepiller <julien@lepiller.eu>
Subject: Re: Multiple sources
Date: Thu, 22 Jul 2021 18:03:45 +0000	[thread overview]
Message-ID: <vDb4mL019-G2K2P-FvqtuVQi3p-CaY1mH5PFbJQc-ZEi3GWfCE1S8CJHx_IEv0-7UWmKCGsewR030piadPcrnMx47SOPQZhAnnfvavyaydw=@protonmail.com> (raw)
In-Reply-To: <20210722190756.263cb40e@tachikoma.lepiller.eu>

> 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!

Thanks Julien!

This is a good way to save myself from full package definition. I now see that other packages define multiple sources in similar way as now I know what to look for.

Though my original question was more about the way the other package managers define sources e.g. PKGBUILD. There the sources are in one "list".
But in the end both definitions are equivalent and they alsoprovide the sums (if not skipped ;-)

source=(https://archive.mozilla.org/pub/firefox/releases/$pkgver/source/firefox-$pkgver.source.tar.xz
        $pkgname.desktop
        "git+https://gitlab.com/${pkgname}-community/browser/common.git#tag=${_common_tag}"
        "git+https://gitlab.com/${pkgname}-community/settings.git#tag=${_settings_tag}")
source_aarch64=("${pkgver}-${pkgrel}_build-arm-libopus.patch::https://raw.githubusercontent.com/archlinuxarm/PKGBUILDs/master/extra/firefox/build-arm-libopus.patch")
sha256sums=('43a943e7d7660c6d7f5b41c95b344b7fd6a4a88ad0bb45dbd844b372ea60d58b'
            '0b28ba4cc2538b7756cb38945230af52e8c4659b2006262da6f3352345a8bed2'
            'SKIP'
            'SKIP')
sha256sums_aarch64=('2d4d91f7e35d0860225084e37ec320ca6cae669f6c9c8fe7735cdbd542e3a7c9')



      reply	other threads:[~2021-07-22 18:09 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
2021-07-22 18:03   ` phodina [this message]

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='vDb4mL019-G2K2P-FvqtuVQi3p-CaY1mH5PFbJQc-ZEi3GWfCE1S8CJHx_IEv0-7UWmKCGsewR030piadPcrnMx47SOPQZhAnnfvavyaydw=@protonmail.com' \
    --to=phodina@protonmail.com \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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).