From: "Ludovic Courtès" <ludo@gnu.org>
To: Phil Beadling <phil@beadling.co.uk>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: --with-source version not honored?
Date: Fri, 29 Oct 2021 16:02:34 +0200 [thread overview]
Message-ID: <87sfwk0w05.fsf@gnu.org> (raw)
In-Reply-To: <CAOvsyQscDyBjqZrD7uzCrOYsaVh+GL1CCD35Qubwg_W8jKvejQ@mail.gmail.com> (Phil Beadling's message of "Sun, 24 Oct 2021 13:11:13 +0100")
Hi,
Phil Beadling <phil@beadling.co.uk> skribis:
> I was able to write a short manifest that avoided the overwriting of the
> original "foobarpy" package in my case, and instead cleanly replace it with
> a newer version specified using "with-source".
>
> By setting, for example, GUIX_FOOBAR_VERSION=1.23 and
> GUIX_TEST_PACKAGE=my-package - I can now create an environment which builds
> the version of foobarpy I want from an https link generated from
> GUIX_FOOBAR_VERSION, and then create a modified version of "my-package"
> with foobarpy replaced, rather than overwritten.
Nice! For the record, there’s a ‘--with-latest’ option that I initially
intended to be ‘--with-version’, but the importer/updater code isn’t
capable enough yet.
> Anyway thought I'd share this here as a template for simple non-recursive
> cases. I suspect it's not a massive effort to make it recursive, when I
> have a moment I'll have a think about that too. Any thoughts on how to
> improve are welcome!
Thanks for sharing!
Ludo’.
next prev parent reply other threads:[~2021-10-29 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 9:18 --with-source version not honored? Phil Beadling
2021-10-20 11:08 ` Julien Lepiller
2021-10-20 11:48 ` zimoun
2021-10-20 19:46 ` Phil
2021-10-21 10:18 ` zimoun
2021-10-21 20:22 ` Ludovic Courtès
2021-10-21 21:17 ` zimoun
2021-10-23 10:04 ` Phil
2021-10-24 12:11 ` Phil Beadling
2021-10-29 14:02 ` Ludovic Courtès [this message]
2021-10-20 19:25 ` Phil
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=87sfwk0w05.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=phil@beadling.co.uk \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).