unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Raghav Gururajan <rg@raghavgururajan.name>, 64120@debbugs.gnu.org
Subject: [bug#64120] [PATCH WIP] gnu: cambalache: Update to 0.12.0.
Date: Sat, 17 Jun 2023 06:43:06 +0200	[thread overview]
Message-ID: <2e30933f05bf8086d23c520ae753604745697c8b.camel@gmail.com> (raw)
In-Reply-To: <87cz1vudyz.fsf@gmail.com>

Am Freitag, dem 16.06.2023 um 20:31 -0400 schrieb Maxim Cournoyer:
> Hello,
> 
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> 
> > * gnu/packages/gnome.scm (cambalache): Update to 0.12.0.
> > [arguments]<#:tests?>: Disable.
> > <#:phases>: Adjust ‘patch-build’ accordingly.  Add ‘fake-cc’.
> > [inputs]: Add gtksourceview-4 and python-pycairo.
> > Replace webkitgtk-with-libsoup2 with webkitgtk and webkitgtk-next.
> 
> Just with webkitgtk-next, no?
No, it actually needs both.

> > [native-inputs]: Add weston.
> > ---
> >  gnu/packages/gnome.scm | 28 ++++++++++++++++++++++------
> >  1 file changed, 22 insertions(+), 6 deletions(-)
> > 
> > diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
> > index a698fdf274..21a5ad424d 100644
> > --- a/gnu/packages/gnome.scm
> > +++ b/gnu/packages/gnome.scm
> > @@ -3303,7 +3303,7 @@ (define-public blueprint-compiler
> >  (define-public cambalache
> >    (package
> >      (name "cambalache")
> > -    (version "0.10.3")
> > +    (version "0.12.0")
> >      (source (origin
> >                (method git-fetch)
> >                (uri (git-reference
> > @@ -3311,7 +3311,7 @@ (define-public cambalache
> >                      (commit version)))
> >                (file-name (git-file-name name version))
> >                (sha256
> > -               (base32
> > "1nq9bvly4dm1xnh90z3b4c5455qpdgm3jgz2155vg2ai23f22vsy"))))
> > +               (base32
> > "12dhc7mx04cpc9qwcvqiplphh3mar7wy6cbkv208j7pcg5fzkqh0"))))
> >      (build-system meson-build-system)
> >      (arguments
> >       (list
> > @@ -3321,6 +3321,7 @@ (define-public cambalache
> >        #:modules '((guix build meson-build-system)
> >                    ((guix build python-build-system) #:prefix
> > python:)
> >                    (guix build utils))
> > +      #:tests? #f                       ; XXX: tests spawn a
> > socket...
> >        #:phases
> >        #~(modify-phases %standard-phases
> >            (add-after 'unpack 'patch-source
> > @@ -3331,8 +3332,16 @@ (define-public cambalache
> >                                    inputs (string-append "bin/"
> > cmd)))))))
> >            (add-after 'unpack 'patch-build
> >              (lambda _
> > +              (substitute* "meson.build"
> > +                (("find_program\\('gtk-update-icon-cache'.*\\)")
> > "")
> > +                (("find_program\\('update-desktop-database'.*\\)")
> > ""))
> >                (substitute* "postinstall.py"
> > +                (("gtk-update-icon-cache") "true")
> >                  (("update-desktop-database") "true"))))
> > +          (add-after 'unpack 'fake-cc
> 
> Nitpick: what is 'fake' here?  I'd just call the phase 'patch-cc'.
'Fake', because cc doesn't exist as a binary.  'patch-cc' follows the
'patch-given-input-file' pattern, which I don't want to imply is
happening here.

> > +            (lambda _
> > +              (substitute* "tools/cmb_init_dev.py"
> > +                (("\"cc") (string-append "\"" #$(cc-for-
> > target))))))
> >            (add-after 'wrap 'python-wrap (assoc-ref
> > python:%standard-phases 'wrap))
> >            (delete 'check)
> >            (add-after 'install 'add-install-to-pythonpath
> > @@ -3372,18 +3381,25 @@ (define-public cambalache
> >             adwaita-icon-theme hicolor-icon-theme
> >             gsettings-desktop-schemas
> >             gtk
> > +           gtksourceview-4
> >             `(,gtk+ "bin")               ; broadwayd
> >             `(,gtk "bin")
> >             libadwaita
> >             libhandy
> >             (librsvg-for-system)
> >             python
> > +           python-pycairo
> >             python-pygobject
> >             python-lxml
> > -           webkitgtk-with-libsoup2))
> > -    (native-inputs (list `(,glib "bin") gobject-introspection
> > -                         gettext-minimal pkg-config
> > -                         python-pytest xorg-server-for-tests))
> > +           webkitgtk
> > +           webkitgtk-next))
> > +    (native-inputs (list `(,glib "bin")
> > +                         gobject-introspection
> > +                         gettext-minimal
> > +                         pkg-config
> > +                         python-pytest
> > +                         weston
> > +                         xorg-server-for-tests))
> > 
> 
> Maybe re-indent as
> 
>  (native-inputs
>   (list one
>         two
>         ...))
Sure.

Cheers

  reply	other threads:[~2023-06-17  4:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 23:38 [bug#64120] [PATCH WIP] gnu: cambalache: Update to 0.12.0 Liliana Marie Prikler
2023-06-17  0:31 ` Maxim Cournoyer
2023-06-17  4:43   ` Liliana Marie Prikler [this message]
2023-06-25 12:46     ` bug#64120: " Liliana Marie Prikler
2023-06-26 13:32       ` [bug#64120] " Maxim Cournoyer

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=2e30933f05bf8086d23c520ae753604745697c8b.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=64120@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=rg@raghavgururajan.name \
    /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).