problems with clc and a new package

Stig E Sandoe <[email protected]>
Newsgroups gmane.lisp.clocc.general,gmane.lisp.cclan.general
Message-ID <[email protected]>
hei,

[this is about clc+deb issues, set followup to the most fitting
 mailing-list or both, please]

was trying today to make one of the bigger and meaner challenges
to clc working again with the new system.  But a simple account:

palomba:/home/stig/Projects# dpkg -i langband-engine_0.1.0-1_all.deb 
Selecting previously deselected package langband-engine.
(Reading database ... 64667 files and directories currently installed.)
Unpacking langband-engine (from langband-engine_0.1.0-1_all.deb) ...
Setting up langband-engine (0.1.0-1) ...
recompiling package langband-engine for implementation cmucl-safe
recompiling package langband-engine for implementation sbcl
/usr/sbin/register-common-lisp-source: Package langband-engine installed

Apparently everything is ok, but the compiles took seconds where
they typically use minutes.  And, not surprisingly I'm unable to find
the actually compiled files.

Let's try to require it (now with defsys3 only, it fails almost the
same way with asdf)
* (require :langband-engine)

; Loading 
#p"/usr/share/common-lisp/repositories/langband/engine/langband-engine.system".


File-error in function COMMON-LISP::INTERNAL-LOAD:
   "modules:langband-engine-library" does not exist.
Restarts:
  0: [CHECK-AGAIN] See if it exists now.
  1: [USE-VALUE  ] Prompt for a new name.
  2: [CONTINUE   ] Return NIL from load of 
#p"modules:langband-engine-library".
  3: [ABORT      ] Return to Top-Level.

Debug  (type H for help)

(COMMON-LISP::INTERNAL-LOAD #p"modules:langband-engine-library" NIL :ERROR 
NIL)


The same applies to if I have and .asd definition.  It then finds the
definition if it uses (asdf:find-system ...) but gets the same
LOAD error above and clc::find-system fails. 

This leads me to another question.  Are there any pioneer packages
that are guaranteed to work because they're tested?

Could error-output in the above compilation be shown in order to 
trace why things screw up there.?

(The code and package I'm trying to get this working is available 
 for testing upon request) 

Any ideas and help would be welcome.  I'm hoping to get v0.1 out
this week and then it'd be nice with deb-packages as well.


Thanks,
-- 
------------------------------------------------------------------
Stig Erik Sandoe     [email protected]    http://www.ii.uib.no/~stig/


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.