unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Inkscape 1.0 upgrade
Date: Wed, 06 May 2020 18:20:39 +0000	[thread overview]
Message-ID: <WhrJ6UlUxIi9Luu-X92y9iXCl9HOgxqvcn5SIT8trYLkDrwQkGQJJd9yZzrsP_hhuYLiMgbWPwAv31lSg87BQl7uw95cWebMULmL1FNZlYY=@elenq.tech> (raw)

Hi all,

With the release of the 1.0 version of Inkscape I wanted to update our package and I'm encountering some problems I'm unable to solve myself.

First, it depends on GDL (Gnome Devtool Libraries) which is not included in Guix so I'm packaging that too. I found an issue I don't know how to solve on it:

GDL makes its bootstrap with this ./autogen.sh:
  https://gitlab.gnome.org/GNOME/gdl/-/blob/master/autogen.sh

That autogen is calling gnome-common's (gnome-common is already on guix) autogen for everything else but, even if I'm able to patch the autogen from GDL to find the correct `sh`, gnome-common's one is still failing because it's looking for `/bin/sh`. I don't find any way to solve this.

Ideas?

Thanks!

This is the GDL package I have at the moment:

(define-public gdl
  (package
    (name "gdl")
    (version "GDL_3_34_0")
    (source (origin
                (method git-fetch)
                (uri (git-reference
                       (url "https://gitlab.gnome.org/GNOME/gdl.git")
                       (commit version)))
                (sha256
                  (base32 "154qcr0x6f68f4q526y87imv0rscmp34n47nk1pp82rsq52h2zna"))))

    (build-system gnu-build-system)
    (inputs `())
    (native-inputs `(("gnome-common" ,gnome-common)
                    ("autoconf" ,autoconf)
                    ("automake" ,automake)
                    ("libtool" ,libtool)
                    ("intltool" ,intltool)
                    ("pkg-config" ,pkg-config)
                    ("gtk-doc" ,gtk-doc)
                    ("which" ,which)))
    (arguments
       `(#:phases
        (modify-phases %standard-phases
         (add-after 'unpack 'autogen
           (lambda _
             (with-directory-excursion "."
                 (for-each make-file-writable (find-files "." ".*"))
                 ;; Use autogen so that 'configure' works.
                 (substitute* "autogen.sh" (("/bin/sh") (which "sh")))
                 (setenv "CONFIG_SHELL" (which "sh"))
                 (invoke "./autogen.sh"))
             #t)))))
    (home-page "...")
    (synopsis "...")
    (description "...")
    (license license:lgpl3+)))


             reply	other threads:[~2020-05-06 21:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 18:20 Ekaitz Zarraga [this message]
2020-05-06 21:54 ` Inkscape 1.0 upgrade Nicolò Balzarotti
2020-05-07  4:39   ` Maxim Cournoyer
2020-05-07  9:21     ` Ekaitz Zarraga

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='WhrJ6UlUxIi9Luu-X92y9iXCl9HOgxqvcn5SIT8trYLkDrwQkGQJJd9yZzrsP_hhuYLiMgbWPwAv31lSg87BQl7uw95cWebMULmL1FNZlYY=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@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).