From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Planning for 0.8.2
Date: Mon, 6 Apr 2015 18:11:46 +0200 [thread overview]
Message-ID: <20150406161146.GA5628@debian> (raw)
In-Reply-To: <87pp7my9qe.fsf@gnu.org>
On Thu, Apr 02, 2015 at 02:51:05PM +0200, Ludovic Courtès wrote:
> Since it was reported that the version in wip-libreoffice builds (only
> with tests disabled), I suppose all the dependencies are there.
I suppose so. But the work in wip-libreoffice is more a quick proof of
concept, getting as quickly as possible to a compiling libreoffice. For the
two dependencies I added, I needed to fill in fields (synopses and/or descrip-
tions), enable the tests and make them work, and add optional inputs (which
apparently were not needed for libreoffice, but should be there for a complete
package, that is presented to the user and not only an input to libreoffice).
As I see it, we should not simply merge the wip-libreoffice branch, but pick
up the added dependencies one by one and turn them into proper patches for
new packages.
Andreas
next prev parent reply other threads:[~2015-04-06 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 15:57 Planning for 0.8.2 Ludovic Courtès
2015-03-31 16:43 ` Andreas Enge
2015-04-01 20:06 ` Ludovic Courtès
2015-04-01 20:57 ` Ricardo Wurmus
2015-04-02 12:51 ` Ludovic Courtès
2015-04-06 16:11 ` Andreas Enge [this message]
2015-04-06 20:04 ` Ludovic Courtès
2015-04-07 11:45 ` John Darrington
2015-03-31 17:07 ` Mark H Weaver
2015-03-31 17:35 ` Eric Bavier
2015-03-31 18:36 ` Mark H Weaver
2015-03-31 20:19 ` Taylan Ulrich Bayırlı/Kammer
2015-04-21 21:33 ` Ludovic Courtès
2015-04-23 22:39 ` Ludovic Courtès
2015-04-24 8:51 ` Taylan Ulrich Bayırlı/Kammer
2015-05-02 20:49 ` Ludovic Courtès
2015-05-07 20:39 ` Ludovic Courtès
2015-05-09 5:05 ` Mark H Weaver
2015-05-09 13:43 ` Ludovic Courtès
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=20150406161146.GA5628@debian \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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.