all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 71599@debbugs.gnu.org, vivien@planete-kraus.eu
Subject: [bug#71599] [PATCH gnome-team 2/2] gnu: tracker-miners: Update to 3.7.3.
Date: Mon, 17 Jun 2024 19:47:24 -0400	[thread overview]
Message-ID: <877cenf7xv.fsf@gmail.com> (raw)
In-Reply-To: <49efdd0fcf3e37ef3656065e163e347ce3eca88c.camel@gmail.com> (Liliana Marie Prikler's message of "Mon, 17 Jun 2024 22:45:10 +0200")

Hi Liliana,

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Am Montag, dem 17.06.2024 um 15:58 -0400 schrieb Maxim Cournoyer:
>> Hi Liliana,
>> 
>> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>> 
>> > * gnu/packages/gnome.scm (tracker-miners): Update to 3.7.3.
>> > [#:configure-flags]: Add “-Dlandlock=disabled”.
>> > ---
>> >  gnu/packages/gnome.scm | 8 ++++++--
>> >  1 file changed, 6 insertions(+), 2 deletions(-)
>> > 
>> > diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
>> > index d7a8f12550..ce20262d2d 100644
>> > --- a/gnu/packages/gnome.scm
>> > +++ b/gnu/packages/gnome.scm
>> > @@ -9766,7 +9766,7 @@ (define-public tracker
>> >  (define-public tracker-miners
>> >    (package
>> >      (name "tracker-miners")
>> > -    (version "3.6.1")
>> > +    (version "3.7.3")
>> >      (source (origin
>> >                (method url-fetch)
>> >                (uri (string-append "mirror://gnome/sources/tracker-
>> > miners/"
>> > @@ -9774,7 +9774,7 @@ (define-public tracker-miners
>> >                                    "/tracker-miners-" version
>> > ".tar.xz"))
>> >                (sha256
>> >                 (base32
>> > -               
>> > "13ljx0birrav728ik3bnlwzgas8q6rbhjbvxp7zzwy6ambafiw7f"))))
>> > +               
>> > "1zm57pih7csgipw3w2b1sgadvfszik70sbz4gr5pn6aw9caqhhz7"))))
>> >      (build-system meson-build-system)
>> >      (arguments
>> >       `(#:glib-or-gtk? #t
>> > @@ -9784,6 +9784,10 @@ (define-public tracker-miners
>> >               (string-append "-Dc_link_args=-Wl,-rpath="
>> >                              (assoc-ref %outputs "out")
>> >                              "/lib/tracker-miners-3.0")
>> > +             ;; TODO: Check if this is only a build-time failure,
>> > +             ;; or add variants to explicitly enable this
>> > features, see also
>> > +             ;;
>> > <https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/300>.
>> 
>> Purely cosmetic and inconsequential, but Ludovic once taught me to
>> use something like:
>> 
>> --8<---------------cut here---------------start------------->8---
>> ;; TODO: Check if this is only a build-time failure, or add variants
>> to
>> ;; explicitly enable this features (see:
>> ;; https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/300).
>> --8<---------------cut here---------------end--------------->8---
>> 
>> which I find elegant.
> In other words, I should not use <> for URIs, but instead use brackets
> for the whole see expression?

The recipe of that scheme is (see: $url) -- the parentheses are
important.

But otherwise, it's just a convention I've seen used often in the code
base (because Ludovic and probably others like me use it as well).

-- 
Thanks,
Maxim

  reply	other threads:[~2024-06-17 23:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 20:25 [bug#71599] [PATCH gnome-team 0/2] Update Tracker Liliana Marie Prikler
2024-06-16 15:44 ` [bug#71599] [PATCH gnome-team 1/2] gnu: tracker: Update to 3.7.3 Liliana Marie Prikler
2024-06-16 20:24 ` [bug#71599] [PATCH gnome-team 2/2] gnu: tracker-miners: " Liliana Marie Prikler
2024-06-17 19:58   ` Maxim Cournoyer
2024-06-17 20:45     ` Liliana Marie Prikler
2024-06-17 23:47       ` Maxim Cournoyer [this message]
2024-06-23 13:54         ` Liliana Marie Prikler
2024-06-17 19:58 ` [bug#71599] [PATCH gnome-team 0/2] Update Tracker 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877cenf7xv.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=71599@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=vivien@planete-kraus.eu \
    /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.