[Gbbopen-developer] portable-threads

[Attila Lendvai]

> Gary King (gwking at metabang.com) subsequently did an ASDF-install for the
> Portable Threads file and added a CLiki page for it.  (GBBopen includes
> a different (non-ASDF) module definition/management system, so we don't
> do much ASDF work/support).  Anyway, if the ASDF-install of GBBopen's
> Portable Threads Interface is broken, Gary is the place to start.


it's not broken, it's just lagging behind and to avoid that in the
future i tried an approach that may be the best of all worlds: i've
tried to add the/a portable-threads.asd to the toplevel dir of the
gbbopen repo.

unfortunately i couldn't make it work without modifying the gbbopen's
sources. the problem is that when gbbopen is loaded, it defines an
asdf system for portable-threads and then (asdf:oos 'asdf:load-op
:portable-thread) errors out when tries to load the system from
portable-threads.asd.

to make it work the portable-threads mini-module should be removed
from the sources and asdf's depends-on should be used for depending on
the p-t system. i'm not sure what you think about this, because there
may be a good reason you are not using asdf and this may be in
conflict with that.

the attached .asd file when put in the gbbopen repo works for the
following commands:

(asdf:operate 'asdf:load-op :portable-threads)
(asdf:operate 'asdf:test-op :portable-threads)

but only as long as the gbbopen system was not load-op'ed yet. this is
not ideal but probably good enough for many lispers who would like to
use the p-t lib and don't want to lag behind (i personally prefer to
use the HEAD of all the code i depend on).


> The on-line & PDF documentation for Portable Threads is not separated
> from GBBopen (and doing so would limit the cross referencing with other
> parts of GBBopen), but we hope that having it as a separate section in a
> larger reference is not a major issue.


yep, i wasn't considering all these... now i think a standalone repo
would be more work then it's worth.


> We view clause 3 of the Apache license as highly desirable protection
> rather than a burden on use/incorporation/distribution of GBBopen (or
> Portable Threads).


thanks for the clarification! i've forwarded it to the author of iolib
who was in doubt.

hth,

-- 
 attila

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: portable-threads.asd
Type: application/octet-stream
Size: 1355 bytes
Desc: not available
Url : http://GBBopen.org/pipermail/gbbopen-developer/attachments/20071115/9fc1a51f/attachment.obj