quilt-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Quilt-dev] [patch 3/8] tac is not portable


From: Josh Boyer
Subject: Re: [Quilt-dev] [patch 3/8] tac is not portable
Date: Thu, 15 Sep 2005 15:10:38 -0500

On Thu, 2005-09-15 at 20:58 +0200, Jean Delvare wrote:
> Hi Josh,
> 
> [Josh Boyer]
> > If soneone does get ambitious enough to do this, my preference would
> > be in python.  I find it more readable than perl.  Plus, gquilt is
> > already written in python, so integration would be easy.
> 
> That second reason sounds wrong to me. A front-end isn't supposed to
> know about the internals of the tool it interfaces with, or both end up
> being so dependent from each other that you obtain a single application
> and other candidate front-ends are likely to die.

Nah, I was thinking more along the lines of gquilt being able to import
a quilt python module.  Not actually tying the two together.  Other
front ends would still call quilt as an executable.

And the first reason is mostly my preference for python anyway :).

> 
> Oh well, jut my opinion I guess.

Everybody's got 'em.  Your's is no less important than mine :).

josh





reply via email to

[Prev in Thread] Current Thread [Next in Thread]