On 21 Aug 2007, at 12:47, Peter Bex wrote:
On Tue, Aug 21, 2007 at 08:44:35AM +0200, Sebasti?n Gonz?lez wrote:
As a side remark, I would propose to delete all those platforms for
which no package is available yet (SUSE, CentOS, Mac Binary, etc.).
There is no point in having such void entries.
Benedikt Rosenau wrote:
Anyway, I propose the following: please keep dependencies between
eggs small.
I disagree; sometimes, it seems better to split common code to libraries
than to have duplication. Dependencies can be hell, but so can duplication.
Further, no mutual dependencies (A needs
Another solution would be to modify salmonella to construct a
dependency graph for all eggs and issue a warning for each dependency
cycle detected. The graph-cycles egg documentation has an example on
how to build a dependency graph, and enumerate all cycles in it.
-Ivan
Sunnan [EMAIL
Ivan Raikov wrote:
Another solution would be to modify salmonella to construct a
dependency graph for all eggs and issue a warning for each dependency
cycle detected.
That would detect the problems, but wouldn't really solve them.
___
Oops, you are right, I was thinking about detection, not prevention
or resolution.
-Ivan
Sunnan [EMAIL PROTECTED] writes:
Ivan Raikov wrote:
Another solution would be to modify salmonella to construct a
dependency graph for all eggs and issue a warning for each dependency
cycle
On Wed, Aug 22, 2007 at 09:16:17AM +0200, Sunnan wrote:
Ivan Raikov wrote:
Another solution would be to modify salmonella to construct a
dependency graph for all eggs and issue a warning for each dependency
cycle detected.
That would detect the problems, but wouldn't really solve them.
Hi,
On Wed, 22 Aug 2007 15:50:49 +0900 Ivan Raikov [EMAIL PROTECTED] wrote:
Another solution would be to modify salmonella to construct a
dependency graph for all eggs and issue a warning for each dependency
cycle detected. The graph-cycles egg documentation has an example on
how to build
This is awesome news! I will be wanting to do that too, pretty soon
(just got my GTA-01 a few days ago). I assume you did this with
OpenEmbedded?
On 8/22/07, john [EMAIL PROTECTED] wrote:
I successfully built Chicken for my OpenMoko phone. It was the first
time I used the cross compilation
On 8/22/07, Shawn Rutledge [EMAIL PROTECTED] wrote:
This is awesome news! I will be wanting to do that too, pretty soon
(just got my GTA-01 a few days ago). I assume you did this with
OpenEmbedded?
Hey, we just got one too :)
It would be nice to have a .bb recipe for chicken
(openembedded).
On Aug 21, 2007, at 8:28 AM, [EMAIL PROTECTED] wrote:
Folks,
It seems to me that syntax-case doesn't support rest arguments (and
keyword arguments, for that matter). It fails to recognize #!rest as
special syntax, and instead interprets it as a variable. Is there
any way
around this?
How
On Wed, Aug 22, 2007 at 08:41:10AM +0200, Sunnan wrote:
Anyway, I propose the following: please keep dependencies between
eggs small.
I disagree; sometimes, it seems better to split common code to libraries
than to have duplication. Dependencies can be hell, but so can duplication.
I have not tried to build with OpenEmbedded yet as I only really need
the runtime library etc which is easy enough to copy across to the
device. Would be good to see how that works!
I used the cross tools generated by MokoMakefile but just did a standard
autoconf build as described on the
On 8/20/07, Kon Lovett [EMAIL PROTECTED] wrote:
On Aug 20, 2007, at 6:46 AM, Alex Queiroz wrote:
Hallo,
After updating to the latest lookup-table egg, I get seg faults
in chicken-meta-setup check, both in x86 and x86-64 Linux boxes.
I don't. If misc-extn is out-of-date then a
hi,
On Sat, Aug 18, 2007 at 02:11:36PM +0200, Hans Bulfone wrote:
hi,
i'm planning to make an incompatible change to the sql:select function
of the sql.egg.
the signature is now:
(sql:select what from where #!optional order-by)
and i want to change it to:
(sql:select what #!key
Good point. Also, the command-line nest-tool could probably be
extended to print a GraphViz (or VCG) representation of the egg
dependencies, using the format-graph egg. Do you want to add that
functionality? I will be more than happy to help with the graph stuff,
though it should be pretty
On Thu, 23 Aug 2007 10:05:33 +0900 Ivan Raikov [EMAIL PROTECTED] wrote:
Good point. Also, the command-line nest-tool could probably be
extended to print a GraphViz (or VCG) representation of the egg
dependencies, using the format-graph egg. Do you want to add that
functionality? I will be
Nice graphs! I was thinking the same thing (but of course, wouldn't
have gotten around to actually doing it).
I think code reuse is generally a good thing. As long as there is no
circular dependency, what's wrong with depending on a few eggs? It's
better than rewriting the parts you need,
SR == Shawn Rutledge [EMAIL PROTECTED] writes:
[...]
SR I think code reuse is generally a good thing. As long as there is
SR no circular dependency, what's wrong with depending on a few eggs?
SR It's better than rewriting the parts you need, right? (and if your
SR few dependencies each
18 matches
Mail list logo
