all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: GNOME updates (was: MTP & Guix)
Date: Thu, 28 Jun 2018 15:08:25 +0200	[thread overview]
Message-ID: <8736x7oy7q.fsf@elephly.net> (raw)
In-Reply-To: <8736xcfcbo.fsf@fastmail.com>


Marius Bakke <mbakke@fastmail.com> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Pierre Neidhardt <ambrevar@gmail.com> writes:
>>>
>>>> Both Gentoo and Guix packages are outdated.
>>>> 1.37 is out.
>>>> GVFS has switched to Meson in the mean time.
>>>> Arch is a little bit more up to date:
>>>>
>>>> https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/gvfs
>>>>
>>>> I guess the above definition could help.
>>>> Anyone giving the update a shot?
>>>
>>> I’m already working on the upgrades to all of GNOME, including the gvfs
>>> upgrade to 1.36.2.
>>
>> This happens on the “core-updates” branch.
>
> Could you create a 'gnome-updates' branch for this?  That makes it
> easier to track the changes, and allows for building it without
> rebuilding the entire world.
>
> We might want to merge it to core-updates rather than build it on its
> own regardless, but at least we have the option.  What do you think?

Changes to the GNOME stack require some changes that are almost
equivalent to rebuilding the world, I’m afraid.  There are changes to
dependencies of GTK+ and Pango, which result in more than 2400 rebuilds.

I have started making these changes on top of core-updates.  Once I’m
done I can push them to a separate branch that could later be merged
into core-updates.

--
Ricardo

  reply	other threads:[~2018-06-29 12:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-23 14:22 MTP & Guix Pierre Neidhardt
2018-06-23 17:53 ` Ricardo Wurmus
2018-06-23 17:59 ` Thompson, David
2018-06-23 18:02   ` Pierre Neidhardt
2018-06-23 18:03     ` Thompson, David
2018-06-23 19:59       ` swedebugia
2018-06-23 20:25         ` Pierre Neidhardt
2018-06-24  9:30           ` Ricardo Wurmus
2018-06-24 10:01             ` Ricardo Wurmus
2018-06-24 15:12               ` Marius Bakke
2018-06-28 13:08                 ` Ricardo Wurmus [this message]
2018-07-05 10:31   ` Chris Marusich
2018-07-07  3:57 ` Maxim Cournoyer
2018-07-07  7:25   ` Pierre Neidhardt
2018-07-08 16:30     ` Maxim Cournoyer
2018-07-08 19:51       ` Pierre Neidhardt

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=8736x7oy7q.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=mbakke@fastmail.com \
    /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.