On Mon, May 29, 2006 at 12:31:49AM -0500, David Moreno Garza wrote:
> Damián Viano wrote:
> > This ended up being a complex/useless package for many reasons.
> > If 1 binary package is created then:
> > * You have several sources
> > * You have a lot of dependencies
> > * Each script requires different handling/setup to work
>
> I really don't see why this is complex or useless.
The mayor problem I see with this approach is the dependency on every
VCS. Right now that would be arch(tla), bazaar, bazaar-ng, bitkeeper(?), cvs,
darcs and svn. Besides python, perl and bash (maybe any sh would do)
which are the languages in which the scripts are written (this is a
non-issue since everything is quite base in a developer desktop).
Another problem is the lack of a orig.tar.gz with proper releases, so
the tar.gz should be created and maintained up to date (which I'm not
sure if is policy compliant) or make it a native package (which still
make it hard to keep it up to date).
> I agree this could be the best approach, to deliver one big package with
> all dependencies covered and all the sources included. If each script
> needs handling/setup, is there anything the user is not supposed to do?
> I mean, the user configuration is obviously needed by such a tool.
Yes, user configuration is fine with me. I just would expect more
consistency about how to configure the scripts provided by one package
(I've been fiddling with the idea of a enable-cia script that given a
repository would set it up (with user provided input) to post to cia).
Maybe I'm just being too demanding on this and we can get along
with a 'you are a developer you should know what you are doing and
setup everything by hand' policy. I may be talked to this.
> > I would like to hear if someone have creative solutions to the
> > problems stated and even would consider retaking the package. Meanwhile
> > I'm dropping the ITP.
>
> I really, really can't see the problem.
Hope you can see my point of view better now, comments are more than
welcome.
Damián Viano(Des)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
