unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Alex Devaure <ajadevaure@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"52956@debbugs.gnu.org" <52956@debbugs.gnu.org>
Subject: [bug#52956] [PATCH] gnu: darktable: update to 3.8.0
Date: Sun, 09 Jan 2022 18:35:13 +0000	[thread overview]
Message-ID: <k8r4z2cDy3Wo5a6GciJ-94u1qUrpBvo93r-JHlXyf1MZLqUcGybd3zujmHURNai7v7vO4JpcVcaaf9gRrad2bvRObsTsAakbavpRsD-i0Wg=@protonmail.com> (raw)
In-Reply-To: <87sftxdshj.fsf@gmail.com>

Hi Alex and Ludo’,

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, January 9th, 2022 at 6:56 AM, Alex Devaure wrote:

> I managed to build darktable with the last lua version (4.5.3) but I
> needed to update the patched for that version.
> During that process, I came to the same question than John's: what is
> the best and least disturbing way to add lua 4.5.3?
>

Glad to hear darktable builds with the newer version of Lua.

However, I realized belatedly that the --with-latest transformation will not inherit the patches of the original package. And, as I would have expected, those patches don't apply cleanly to the new 5.4.3 source. I haven't had a chance to investigate, and likely won't be able to for a bit (still catching up on other patches I have).

As for how to introduce the new version, my guess (now that the patches needed to be updated) would be to have a lua-5.4 (or called lua-next) package. If it is just the patches that need to be updated, lua (the 5.3 version) could inherit from lua-5.4 adjusting the source field for that version and using the original patches. Assuming this doesn't cause rebuilds of the lua packages, that is. If more changes are needed, then lua-5.4 would just stand separate from the lua <= 5.3 version set.

John




  reply	other threads:[~2022-01-09 18:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02  9:43 [bug#52956] [PATCH] gnu: darktable: update to 3.8.0 Alex Devaure
2022-01-02 17:21 ` John Kehayias via Guix-patches via
2022-01-08 21:59   ` Ludovic Courtès
2022-01-08 22:54     ` John Kehayias via Guix-patches via
2022-01-09 11:56       ` Alex Devaure
2022-01-09 18:35         ` John Kehayias via Guix-patches via [this message]
2022-01-09 21:14           ` Alex Devaure
2022-01-11 12:25             ` Alex Devaure
2022-01-16 22:21               ` Ludovic Courtès
2022-01-17 21:08                 ` Alex Devaure
2022-01-19 20:44                   ` bug#52956: " Ludovic Courtès

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='k8r4z2cDy3Wo5a6GciJ-94u1qUrpBvo93r-JHlXyf1MZLqUcGybd3zujmHURNai7v7vO4JpcVcaaf9gRrad2bvRObsTsAakbavpRsD-i0Wg=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=52956@debbugs.gnu.org \
    --cc=ajadevaure@gmail.com \
    --cc=john.kehayias@protonmail.com \
    --cc=ludo@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.
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).