[Top][All Lists]

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

Re: [Chicken-users] script to generate html from wiki-formatted text?

From: Christian Kellermann
Subject: Re: [Chicken-users] script to generate html from wiki-formatted text?
Date: Thu, 1 Sep 2011 11:40:33 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

* Alaric Snell-Pym <address@hidden> [110901 11:27]:
> Hash: SHA1
> On 09/01/2011 10:08 AM, Peter Bex wrote:
> > If you have suggestions on how to improve this without listing all the
> > package names of all the distributions out there, that would of course
> > be much appreciated!
> I suppose the only widely portable way to identify a library would be by
> pointing at the actual underlying homepage of the library...

I think this all is a non issue in practise when it comes to
individual eggs that do not have many dependencies. For example: I
want to install libexif bindings for finding some digital camera
images on my disk. Do I need libexif? Of course. In this case it is
obvious to the user. 

The obscurity sets in, when people install more complex libraries that
themselves depend on eggs with external dependencies.

Maybe adding a simple clause like:

(depends-on-external "libexif" source: "";)

to the .meta file (of libexif in this case) which can be queried by 

So the user has a chance to get a complete list of all dependencies in
advance instead of having to trip on each one by one.

Does this make sense?

Who can (make) the muddy water (clear)? Let it be still, and it will
gradually become clear. Who can secure the condition of rest? Let
movement go on, and the condition of rest will gradually arise.
 -- Lao Tse. 

reply via email to

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