From: Vinicius Monego <monego@posteo.net>
To: Ferran Pujol Camins <ferranpujolcamins@gmail.com>
Cc: 72297@debbugs.gnu.org
Subject: [bug#72297] [PATCH] gnu: libdjinterop: Update to 0.21.0.
Date: Sat, 27 Jul 2024 18:05:07 +0000 [thread overview]
Message-ID: <d7f84ff68e60fc0597c6829ae3234cc392ae3334.camel@posteo.net> (raw)
In-Reply-To: <CAP9NH=EjjEA2SNsgBfMOE4DDuyiTWW-79+m0ZAVKY=edh_PaZw@mail.gmail.com>
Em sáb, 2024-07-27 às 19:02 +0200, Ferran Pujol Camins escreveu:
[...]
>
> > QA is likely to break here, so this update should wait for the next
> > release of Mixxx, which will bump libdjinterop to 0.21.0.
> >
>
>
> I see. My goal was precisely to have v0.21.0 packaged so I could set
> a guix shell to develop with mixxx main branch. How is this usually
> handled?
>
Given that this is simple version bump that doesn't need significant
changes, you can spawn a shell with --with-commit=package=version e.g.
guix shell -D mixxx --with-commit=libdjinterop=0.21.0
See "Package Transformation Options" in the manual:
https://guix.gnu.org/manual/en/html_node/Package-Transformation-Options.html
But if you needed more complex changes in the inputs, you could use
your own packages defined in local files. Create a directory with
Scheme files containing package definitions and add that directory to
the GUIX_PACKAGE_PATH environment variable. Let's say you locally
define 'mylibdjinterop', then you can use a transformation like
guix shell -D mixxx --with-input=libdjinterop=mylibdjinterop
You can find a tutorial for this here:
https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/
Vinicius
next prev parent reply other threads:[~2024-07-27 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 14:00 [bug#72297] [PATCH] gnu: libdjinterop: Update to 0.21.0 Ferran Pujol Camins
2024-07-26 22:25 ` Vinicius Monego
2024-07-27 17:02 ` Ferran Pujol Camins
2024-07-27 18:05 ` Vinicius Monego [this message]
2024-07-28 9:56 ` Ferran Pujol Camins
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=d7f84ff68e60fc0597c6829ae3234cc392ae3334.camel@posteo.net \
--to=monego@posteo.net \
--cc=72297@debbugs.gnu.org \
--cc=ferranpujolcamins@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.