From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: To-do lists Date: Fri, 18 Jan 2013 14:16:26 +0100 Message-ID: <201301181416.26983.andreas@enge.fr> References: <874nifuuad.fsf@karetnikov.org> <201301181118.29250.andreas@enge.fr> <87obgm7i4v.fsf_-_@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-01=_qsU+QqvekUcTsys" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:56167) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TwBoB-0007JO-04 for bug-guix@gnu.org; Fri, 18 Jan 2013 08:16:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TwBo8-00070k-0g for bug-guix@gnu.org; Fri, 18 Jan 2013 08:16:34 -0500 In-Reply-To: <87obgm7i4v.fsf_-_@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?utf-8?q?Court=C3=A8s?= Cc: bug-guix@gnu.org --Boundary-01=_qsU+QqvekUcTsys Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Am Freitag, 18. Januar 2013 schrieb Ludovic Court=C3=A8s: > Another thing we can do to avoid duplicated work, is to commit and push > individual packages as soon as we have them. For instance, as soon as > you have a working libextractor, go ahead and push it. That is what I do. But I am not fond of pushing packages for which I would= =20 still like to add more inputs; it is possible to push libextractor without= =20 lots of optional dependencies. This is what my proposed patch for vorbis- tools does, there is a FIXME explaining which inputs are missing. But then= =20 there is a higher risk of forgetting to add them. Otherwise said, currently I am doing a depth-first exploration of the=20 dependency graph, but one could do something closer to breadth-first. > Or maybe we should use an Org file somewhere, or a wiki, or some sort of > locally-hosted Web 2.0 task management thing. Anything would be fine for me as long as it is easy. Maybe a wiki would be= =20 easiest for the time being. Andreas --Boundary-01=_qsU+QqvekUcTsys Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Am Freitag,= 18. Januar 2013 schrieb Ludovic Court=C3=A8s:

> Anothe= r thing we can do to avoid duplicated work, is to commit and push

> indivi= dual packages as soon as we have them. For instance, as soon as

> you ha= ve a working libextractor, go ahead and push it.

&nb= sp;

That is wha= t I do. But I am not fond of pushing packages for which I would still like = to add more inputs; it is possible to push libextractor without lots of opt= ional dependencies. This is what my proposed patch for vorbis-tools does, t= here is a FIXME explaining which inputs are missing. But then there is a hi= gher risk of forgetting to add them.

&nb= sp;

Otherwise s= aid, currently I am doing a depth-first exploration of the dependency graph= , but one could do something closer to breadth-first.

&nb= sp;

> Or may= be we should use an Org file somewhere, or a wiki, or some sort of

> locall= y-hosted Web 2.0 task management thing.

&nb= sp;

Anything wo= uld be fine for me as long as it is easy. Maybe a wiki would be easiest for= the time being.

&nb= sp;

Andreas

&nb= sp;

--Boundary-01=_qsU+QqvekUcTsys--