<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Henrik Hjelte wrote:
<blockquote
cite="mid:50e8e4f60908220028h3f38f49cqbe1ab9cf1051585e@mail.gmail.com"
type="cite">
<pre wrap="">On Fri, Aug 21, 2009 at 4:19 PM, Jeff
Cunningham<a class="moz-txt-link-rfc2396E" href="mailto:j.k.cunningham@comcast.net"><j.k.cunningham@comcast.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thanks, Henrik. That was exactly my problem.
So, before I contact the CFFI developers and ask them to fix this annoying
case of identity theft, do you know if anyone has already done so?
</pre>
</blockquote>
<pre wrap=""><!---->
I think that someone contacted the clbuild maintainers, but I don't
think someone has complained to the cffi developers which I think
would be the right thing to do. It would be one thing if cffi-compat
could compile elephant, but until that time this problem steals a lot
of time for people, you are not the first victim.
/Henrik
_______________________________________________
elephant-devel site list
<a class="moz-txt-link-abbreviated" href="mailto:elephant-devel@common-lisp.net">elephant-devel@common-lisp.net</a>
<a class="moz-txt-link-freetext" href="http://common-lisp.net/mailman/listinfo/elephant-devel">http://common-lisp.net/mailman/listinfo/elephant-devel</a>
</pre>
</blockquote>
I'm working on them, but I could use some help. Hans Hubner weighed in
on my side, but mostly they want go this route:<br>
<br>
<pre wrap="">Elephant breaks UFFI's abstractions and assumes SB-ALIEN is being used
behind the scenes. That naturally breaks with cffi-uffi-compat.
</pre>
<br>
They want you to either fix this, or better yet, convert over entirely
to CFFI. <br>
<br>
It seems clear to me that whether they are right or wrong, you ought to
be able to expect that another package not break your package via the
ASDF system, when yours has no dependency on theirs. <br>
<br>
This is a basic Lisp ecosystem issue that has dogged the Lisp community
for years. Somehow we have got to get past this stuff or we'll never
get anywhere. Its like the rule of law: people will never venture very
much if they can't count on a system supporting them to protect what
they venture. <br>
<br>
--Jeff<br>
<br>
<br>
</body>
</html>