From: "Jakub Kądziołka" <kuba@kadziolka.net>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 39723-done@debbugs.gnu.org
Subject: bug#39723: [PATCH] gnu: swig: Update to 4.0.1.
Date: Sat, 22 Feb 2020 18:11:56 +0100 [thread overview]
Message-ID: <20200222171156.4fjgcfm4keelgklq@gravity> (raw)
In-Reply-To: <20200221214319.14837-1-arunisaac@systemreboot.net>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
On Sat, Feb 22, 2020 at 03:13:18AM +0530, Arun Isaac wrote:
> * gnu/packages/swig.scm (swig): Update to 4.0.1.
> [source]: Remove swig-guile-gc.patch.
> [arguments]: Remove set-env phase.
> [inputs]: Replace guile-2.0 with guile-3.0.
> * gnu/packages/patches/swig-guile-gc.patch: Delete file.
> * gnu/local.mk (dist_patch_DATA): Unregister it.
Hi,
swig is depended upon by 5206 packages. This means that any updates will
have to go through the core-updates branch. The branch has swig 4.0.1
since this December. Sorry for the duplicated effort...
You might want to send a patch to build swig with guile-3.0 instead of
the guile-2.2 used currently on core-updates. If you decide to do so,
please use [PATCH core-updates] in the subject. You can do this easily
by passing --subject-prefix="PATCH core-updates" to git format-patch.
See point 8 of `info '(guix)Submitting Patches'` for more details.
Regards,
Jakub Kądziołka
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-02-22 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 21:43 [bug#39723] [PATCH] gnu: swig: Update to 4.0.1 Arun Isaac
2020-02-22 17:11 ` Jakub Kądziołka [this message]
2020-02-22 17:50 ` Arun Isaac
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=20200222171156.4fjgcfm4keelgklq@gravity \
--to=kuba@kadziolka.net \
--cc=39723-done@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/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.