Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-22 Thread Jeff Cunningham
Luís Oliveira wrote: That of course is a more general problem that should be solved with something like this: . I have seen plenty of people taking advantage of the fact that CFFI-UFFI-COMPAT can easily be used as a drop-in replacement for UFFI. I have never

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-22 Thread Luís Oliveira
On Sat, Aug 22, 2009 at 3:26 PM, Jeff Cunningham wrote: > As it stands, even using asdf:*central-registry* is a problem, because > there's no way to use both. Since they both have the same name only one can > exist with it using the asdf system in any normal fashion. That of course is a more gene

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-22 Thread Jeff Cunningham
Luís Oliveira wrote: uffi.asd was added by popular demand. (Or maybe it was just *one* user, I don't recall.) I'd be glad to rename it, but as I've mentioned in a previous email, I'm worried that it'd do more harm than good. Suggestions on how to solve the problem are most welcome. 1. A

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Daniel Herring
On Fri, 21 Aug 2009, Cunningham, Jeffrey K. wrote: From: Luís Oliveira As Daniel Herring hinted, one way you can solve this problem is to setup asdf:*central-registry* such that UFFI's uffi.asd takes precedence over the clbuild/systems/uffi.asd one. Would that work for you? You are right - it

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Luís Oliveira
On Sat, Aug 22, 2009 at 2:36 AM, Hans Hübner wrote: > I use an automated mechanism to setup my asdf:*central-registry* and > it would be a pain if I had to change that.  I find it offensive if > some library decides that it is "better" than something else and makes > that something else unusable o

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Hans Hübner
On Fri, Aug 21, 2009 at 19:10, Luís Oliveira wrote: > As Daniel Herring hinted, one way you can solve this problem is to > setup asdf:*central-registry* such that UFFI's uffi.asd takes > precedence over the clbuild/systems/uffi.asd one. Would that work for > you? I use an automated mechanism to s

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Luís Oliveira
On Sat, Aug 22, 2009 at 2:20 AM, Cunningham, Jeffrey K. wrote: > What do you suggest is the best course to follow? Fixing Elephant, either by porting the whole thing to CFFI -- or (slightly easier) just the SB-ALIEN bits -- seems like the right thing to do. -- Luís Oliveira http://student.dei.u

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Cunningham, Jeffrey K.
-Original Message- From: Luís Oliveira [mailto:luis...@gmail.com] Sent: Friday, August 21, 2009 5:33 PM To: Cunningham, Jeffrey K. Cc: cffi-devel@common-lisp.net; clbuild-devel Subject: Re: [cffi-devel] uffi.asd vs uffi-compat.asd > If you are interested in the improving the L

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Luís Oliveira
On Fri, Aug 21, 2009 at 11:23 PM, Cunningham, Jeffrey K. wrote: > You are right - it would solve the problem. But it leaves > library compatibility in that awful state that requires too > much arcane information to be known to write decent > auto-setup tools. But don't you think that in the long ru

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Cunningham, Jeffrey K.
-Original Message- From: cffi-devel-boun...@common-lisp.net [mailto:cffi-devel-boun...@common-lisp.net] On Behalf Of Luís Oliveira Sent: Friday, August 21, 2009 4:11 PM To: Jeff Cunningham Cc: cffi-devel@common-lisp.net Subject: Re: [cffi-devel] uffi.asd vs uffi-compat.asd > As Dan

[cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Cunningham, Jeffrey K.
On Fri, Aug 21, 2009 at 4:01 PM, Jeff Cunningham > I would gladly rename it. It would work just as well for its original > purpose, since as long as you create a uffi.asd symlink, > (asdf:find-system :uffi) will pick it up. However, I suspect there > might be other code in clbuild that does in fa

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Luís Oliveira
On Fri, Aug 21, 2009 at 4:01 PM, Jeff Cunningham wrote: > Is there a way that this can be resolved? It seems that both libraries > should be able to coexist on a system, as there are applications which > expect them to be there. It also seems that UFFI has a prior claim to > its own name for a syst

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread dherring
Luís Oliveira wrote: > On Fri, Aug 21, 2009 at 4:01 PM, Jeff Cunningham > wrote: >> I just tried to install elephant and ran into an annoying problem which >> could only be resolved by renaming the cffi/uffi-compat/uffi.asd to >> uffi-compat.asd. The problem seems to be one of identity theft, sinc

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Luís Oliveira
On Fri, Aug 21, 2009 at 10:00 PM, Attila Lendvai wrote: > just a note: not everybody is using symlinks to manage asdf systems. > with a different name a .asd scanner would miss it... That's the goal. :-) -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Attila Lendvai
> I would gladly rename it. It would work just as well for its original > purpose, since as long as you create a uffi.asd symlink, just a note: not everybody is using symlinks to manage asdf systems. with a different name a .asd scanner would miss it... just my 0.02, -- attila ___

Re: [cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Luís Oliveira
On Fri, Aug 21, 2009 at 4:01 PM, Jeff Cunningham wrote: > I just tried to install elephant and ran into an annoying problem which > could only be resolved by renaming the cffi/uffi-compat/uffi.asd to > uffi-compat.asd. The problem seems to be one of identity theft, since > elephant uses uffi, and

[cffi-devel] uffi.asd vs uffi-compat.asd

2009-08-21 Thread Jeff Cunningham
I just tried to install elephant and ran into an annoying problem which could only be resolved by renaming the cffi/uffi-compat/uffi.asd to uffi-compat.asd. The problem seems to be one of identity theft, since elephant uses uffi, and it was picking up the cffi compatibility code (which does not