unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: rennes@openmailbox.org
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add libzapojit.
Date: Thu, 25 Feb 2016 14:35:25 -0500	[thread overview]
Message-ID: <20160225193525.GC18435@jasmine> (raw)
In-Reply-To: <40322f17c87a911d6621a9fbfa070c37@openmailbox.org>

On Thu, Feb 25, 2016 at 07:59:51AM -0600, rennes@openmailbox.org wrote:
> On 2016-02-24 19:14, Leo Famulari wrote:
> >On Sat, Feb 20, 2016 at 04:25:37PM -0600, rennes@openmailbox.org wrote:
> >>Hi,
> >>
> >>i attached libzapojit patch for review.
> >
> >Thanks for the patch!
> >
> >>
> >>This is a library for accessing SkyDrive and Hotmail, necessary for
> >>documents manager(GNOME apps).
> >
> >Is the documents manager already packaged?
> >
> >If so, I assume libzapojit is working for you?
> >
> >If not, I might want to merge it anyways to encourage further work on
> >GNOME stuff by everyone :)
> >
> >>* gnu/packages/gnome.scm (libzapojit): New variable.
> >
> >[...]
> >
> >>+    (build-system gnu-build-system)
> >
> >I can't tell — should it use glib-or-gtk-build-system instead? It seems
> >to build fine as-is, but I wonder because it uses some GLib stuff.
> >
> >Looks good aside from these questions.
> 
> Hi,
> 
> GNOME documents is not yet packaged, I started packaging requirements, in
> this sequence. GNOME documents has several requirements not packaged. or
> what is the best strategy to do so?

One strategy is to package the entire dependency graph of GNOME
Documents privately, and then submit them when the whole thing is ready.

You could modify that strategy by sending each package for review as you
go, but without merging them into master until everything is done.

You could modify it again by having us commit each package to master
when it looks good, and then making adjustments later. The benefit of
this is that it's very easy for other people to know how to help you
with this project, for example by packaging some of the dependencies on
their own.

I'm not sure what the best strategy is. It's up to you and anyone else
who comments :) Please advise!

  reply	other threads:[~2016-02-25 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 22:25 [PATCH] gnu: Add libzapojit rennes
2016-02-25  1:14 ` Leo Famulari
2016-02-25 13:59   ` rennes
2016-02-25 19:35     ` Leo Famulari [this message]
2016-02-25 19:59       ` 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=20160225193525.GC18435@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=rennes@openmailbox.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).