From: John Darrington <john@darrington.wattle.id.au>
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 08:54:27 +0100 [thread overview]
Message-ID: <20170104075427.GA23394@jocasta.intra> (raw)
In-Reply-To: <1483510879.954299.836743273.74B0D1E7@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
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.
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.
Perhaps we should keep both releases in Guix as seperate packages?
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-01-04 7:54 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 [this message]
2017-01-04 7:57 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170104075427.GA23394@jocasta.intra \
--to=john@darrington.wattle.id.au \
--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 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.