Re: [Chicken-users] Re: getopt, getopt_long?

[felix winkelmann]

On Fri, Jul 11, 2008 at 9:50 AM, Ivan Raikov <address@hidden> wrote:
>
>  I would like to have a single egg description file that is simply an
> alist with make rules, file groups and installation locations. You can
> call it .meta or whatever else you like.
>

Right, ok.

>
>   I am not proposing a package management system, why do you keep
> insisting on that?

Perhaps I'm just misunderstanding your intentions. I'd say `chicken-setup'
already is a package-management tool in its current incarnation.
I also don't want to start an argument about it. The current implementation
has accumulated many features that make it (IMHO) hard to change
and maintain. I just want to avoid that in the future.

> I just want chicken-setup to be flexible enough to
> be run by package building tools. In order to do that, you need to
> support abstractions for fetching source files, make rules, file
> categories and installation locations. If I have that, I am willing to
> write a .setup transition tool that can automatically translate 90% of
> the current .meta and .setup files to the new egg description
> language.

Great! Perhaps we can find someone who is willing to implement
the low-level layer.


cheers,
felix