From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: PATCH: LibreOffice
Date: Sun, 31 May 2015 20:19:16 +0200 [thread overview]
Message-ID: <20150531181916.GA3182@debian> (raw)
In-Reply-To: <87pp5gtzi1.fsf@netris.org>
Hi Marc,
thanks for your comments!
On Sun, May 31, 2015 at 01:42:30PM -0400, Mark H Weaver wrote:
> (gnu packages which) has not existed since early March. 'which' was
> moved to (gnu packages base) in ce0614ddb0.
That is interesting. I think it worked for me since I still had which.go
in my tree.
> The 'configure' and 'build' phases are misleadingly named, given what
> they actually do. However, I wonder whether this package is needed at
> all. How about just including the 'origin' as an input to
> 'libreoffice', unpack it after the 'unpack' phase, and then let the
> standard phases in libreoffice take care of the usual patching jobs.
> Would that work?
From what I understood, no. Libreoffice seems to expect the tarball in a
special location, and the libreoffice build system takes care of unpacking it.
But I am not a 100% sure whether the patching we do is needed or not;
maybe everything would compile with the unchanged tarball. One of the problems
is that the patching changes dates and causes an "autoreconf" (or similar)
after unpacking anyway, so part of the /bin/sh-patching is reverted.
Andreas
next prev parent reply other threads:[~2015-05-31 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 9:08 PATCH: LibreOffice Andreas Enge
2015-05-31 17:42 ` Mark H Weaver
2015-05-31 18:19 ` Andreas Enge [this message]
2015-05-31 20:32 ` Ludovic Courtès
2015-06-01 12:52 ` John Darrington
2015-06-01 19:40 ` Ludovic Courtès
2015-06-01 19:50 ` Andreas Enge
2015-06-01 19:56 ` Andreas Enge
2015-06-03 12:39 ` Andreas Enge
2015-06-04 20:37 ` Ludovic Courtès
2015-06-04 20:56 ` Andreas Enge
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=20150531181916.GA3182@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).