unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: libreoffice: Update to 5.1.6.2.
Date: Wed, 4 Jan 2017 02:57:32 -0500	[thread overview]
Message-ID: <20170104075732.GA1083@jasmine> (raw)
In-Reply-To: <1483510879.954299.836743273.74B0D1E7@webmail.messagingengine.com>

On Wed, Jan 04, 2017 at 12:21:19AM -0600, Alex Griffin wrote:
> On Tue, Jan 3, 2017, at 08:52 PM, Alex Griffin wrote:
> > This patch updates libreoffice to 5.1.6.2, the latest release from their
> > "still" branch (long-term support, stable). Although I think it will be
> > EOL soon, so updating to 5.2.4.2 would be better... if someone else were
> > up to it. The only reason I didn't try moving straight to that version
> > is because my laptop takes ~8 hours to build libreoffice.

I'm currently building libreoffice with your patch :)

> Apologies, this email was poorly worded. Basically, LibreOffice has 2
> supported releases: a "fresh" release (5.2.4.2) and a "still" release
> (5.1.6.2). Since Guix already had the "still" release packaged,
> upgrading to 5.1.6.2 just required a version bump. Upgrading to "fresh"
> requires more work, which I don't really want to do myself because I
> would have to wait way too long to iterate on my changes.

I looked into this recently. I saw that there are many
LibreOffice-specific packages that we should look into updating as well,
especially when we try to update to the "fresh" release. But, as you
mentioned, it's hard to stay motivated to work on the LibreOffice
package because of how long it takes to build.

For now, the "still" release is fine.

  parent reply	other threads:[~2017-01-04  7:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  2:52 [PATCH] gnu: libreoffice: Update to 5.1.6.2 Alex Griffin
2017-01-04  6:21 ` Alex Griffin
2017-01-04  7:54   ` John Darrington
2017-01-04  7:57   ` Leo Famulari [this message]
2017-01-04 19:38 ` Leo Famulari

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=20170104075732.GA1083@jasmine \
    --to=leo@famulari.name \
    --cc=a@ajgrf.com \
    --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).