Re: Extracting a UIOP's manual

2019-03-26 Thread Didier Verna
"Robert Goldman"  wrote:

> On 15 Aug 2018, at 8:59, Hugo Ishimaru wrote:
>
>  Hi all,
>
>  I have extracted a UIOP's manual from docstrings:
>  https://privet-kitty.github.io/etc/uiop.html It's not perfect in any
>  means as docstring isn't written in a markup langugage, but will be
>  at least a comprehensive reference. The relevant fork of ASDF is in
>  Github: https://github.com/privet-kitty/asdf/tree/uiop-man/uiop/doc
>  The greater part of the generation conforms to that of Alexandria,
>  which depends on SBCL (sb-texinfo).
>
>  I send this mail as it states
>  > Help wanted extracting working documentation from UIOP's docstrings. 
>  in README.md though I might not understand a historical context.
>
>  Regards
>  Hugo Ishimaru
>
> Thank you very, very much! I am going to be away from ASDF for about a
> week now, but I will look for it as soon as I get back. This will be
> very helpful indeed!


  FWIW, Quickref now also documents ASDF and UIOP.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: long-description

2019-02-21 Thread Didier Verna
Eitaro Fukamachi  écrivait:

> To be honest, I'm not a big fan of it anymore and I don't follow it in
> my recent products. I'm willing to delete the code from CL-Project,
> though I have nothing I can do for existing projects.

  Not a big fan either. What I usually do is use the description slot as
  a one-liner, and the long-description one as some kind of abstract
  about the project. My README files are usually longer, more elaborate.

  Also, FYI, Quickref uses README files as an introduction section in
  the generated reference manuals automatically. This is a
  functionality that I plan to move to Declt at some point. Having a
  whole README file in the long-description slot would look weird in
  Quickref-generated documentation.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: Timing compilation

2018-12-05 Thread Didier Verna
"Robert Goldman"  écrivait:

> This is yet another problem that comes from the fact that the build
> plans are linear, instead of hierarchical -- for example there's no
> subsequence that is identifiable as being the set of operations for a
> particular module.
>
> Logically speaking, there's a tree structure in the build process that
> is what you need, but I don't believe that there are any facilities in
> ASDF to recover that tree structure.
>
> This may be the best you can do.

  I think I'll go with Faré's suggestion, scripting it for every library
  and changing the cache directory every time.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: Timing compilation

2018-12-05 Thread Didier Verna
"Robert Goldman"  écrivait:

> Depending on the host lisp you are using, couldn't you wrap the calls
> to COMPILE-FILE and LOAD in code that times those operation?

  I could, but since I want per-library numbers, I would need to
  reconstruct that information afterwards...

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: Timing compilation

2018-12-05 Thread Didier Verna
François-René ÐVB Rideau écrivait:

> Simplest  method:
> 1- load the dependencies, possibly using (asdf:operate :prepare-op s)
> 2- (time (asdf:make s))

  Nice, thank you. If I want to time separately the compilation and
  loading phases of several libraries (which may depend on each other)
  however, I would need to restart my session every single time. Another
  way to do this and, say, report the timings to a file?

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Timing compilation

2018-12-05 Thread Didier Verna


  Hello,

I would like to collect information about the time it takes to compile
an ASDF system (possibly also load it), dependencies excluded. I'm
thinking there's probably a way to do this by :around'ing compile-op, or
something like that, but if someone already has a clear view on how to
make this happen, I'd be grateful for the time spared!

Thanks.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: locating a source directory

2018-06-08 Thread Didier Verna
I wrote:

> I would like to find the source directory of an installed ASDF system
> even if it's not loaded and even if some of its dependencies are not
> installed (so it couldn't be loaded anyway). It seems that I can't use
> SYSTEM-SOURCE-DIRECTORY in such a case. What should I do?

  Replying to myself (I often do that when I'm alone :-D) it seems that
  LOCATE-SYSTEM could do the job...

-- 
Resistance is futile. You will be jazzimilated.

Jazz site:   http://www.didierverna.com
Other sites: http://www.didierverna.info



locating a source directory

2018-06-08 Thread Didier Verna


  Hello,

I would like to find the source directory of an installed ASDF system
even if it's not loaded and even if some of its dependencies are not
installed (so it couldn't be loaded anyway). It seems that I can't use
SYSTEM-SOURCE-DIRECTORY in such a case. What should I do?

Thanks!

-- 
Resistance is futile. You will be jazzimilated.

Jazz site:   http://www.didierverna.com
Other sites: http://www.didierverna.info



Re: Removing content from README.md

2016-08-05 Thread Didier Verna
Robert Goldman  wrote:

> I just looked over that README, and realized that it was not
> maintained.  I quickly concluded that I do not have the resources to
> maintain both this file and the HTML file at
> https://common-lisp.net/project/asdf/, and the latter is what I have
> been updating with new releases.  So the former must go.

  FWIW, I took the habit of maintaining only one documentation source
  (in Texinfo format) and extracting README files and others (such as
  INSTALL) from there, hence also avoiding the maintenance of duplicate
  information.

  It's easy to extract specific chapters from an Info file. For
  instance, here's a Makefile target that I have in Clon:

INSTALL: doc/$(PROJECT)-user.info
info --file=./doc/$(PROJECT)-user.info  \
 -n Installation\
 -n Configuration   \
 -n 'Non-ANSI Features' \
 -n 'Supported Platforms'   \
 --output=$@
perl -pi -e 's/^File:.*\n//g' $@


-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: :FEATURE dependency-def

2016-05-20 Thread Didier Verna
François-René ÐVB Rideau wrote:

> The traditional solution is to load a file that fails.  i.e. create a
> file unsupported-implementation.lisp that has an (error ...) form and
> in your asd file, use a component (:file "unsupported-implementation"
> :if-feature (:not :sbcl))

  Hmmm, ok but then, if you're to error in a Lisp file proper, why use
  the ASDF logic at all? I mean, why not just depend on the file as a
  regular one and perform all the tests that you need from Lisp code?

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



[Q] figuring out a system / source file

2015-11-24 Thread Didier Verna

  Hello,

starting from a file currently being processed (as per either
*compile-file-truename* or *load-truename*), how can I retrieve the ASDF
system currently being processed, and ultimately, the corresponding
source file component (when *load-truename* returns a fasl) ?

Thanks.

-- 
My new Jazz CD entitled "Roots and Leaves" is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: License field

2015-10-20 Thread Didier Verna
François-René ÐVB Rideau écrivait:

> I was considering just a string for now

  FWIW, I'm also in favor of strings. Using symbols is risky for
  case-sensitiveness.

-- 
My new Jazz CD entitled "Roots and Leaves" is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: License field

2015-10-17 Thread Didier Verna
François-René ÐVB Rideau écrivait:

> I propose we document that the license field should if possible
> contain an identifier from
>   http://spdx.org/licenses/
>   http://esr.ibiblio.org/?p=6867

  Good idea, although it seems to be missing the GNU All Permissive
  license (the submission process looks quite cumbersome). 

-- 
My new Jazz CD entitled "Roots and Leaves" is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: License field

2015-10-17 Thread Didier Verna
J'écrivais:

>   Good idea, although it seems to be missing the GNU All Permissive
>   license (the submission process looks quite cumbersome).

  Ended up doing it anyway.

-- 
My new Jazz CD entitled "Roots and Leaves" is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: :require dependency

2015-06-29 Thread Didier Verna
Robert Goldman rpgold...@sift.net wrote:

 According to the manual REQUIRE-SYSTEM is ... a version of
 @code{load-system} that skips trying to update systems that are
 already loaded.

 There is no REQUIRE-OP.

 There is a REQUIRE-SYSTEM which is a system whose loading is handled
 by REQUIRE instead of native ASDF.

  OK, this is what I figured in the meantime. But then, this seems to
  contradict what the manual says (the part you're mentioning above).

 This might be useful, e.g., on ACL, which has many bundled modules
 which are loaded by REQUIRE. I'm not sure there is a common
 implementation-independent use case, since people aren't distributing
 a lot of code to be loaded with REQUIRE, AFAICT.

  I guess it's mostly useful for implementation-specific libraries. I
  use it for sb-grovel for instance.

 Hope that helps.  Sorry for the late answer: we've been grappling with
 some knotty bugs on Windows.

  No worries. When I have bugs on windows, I usually close the blinds :-D

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



:require dependency

2015-06-25 Thread Didier Verna

  Hello,

can somebody explain to me what is the :require dependency specification,
and how it compares to just a simple-component-name ?

Thanks.

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: The dictatorship of versioning

2015-06-16 Thread Didier Verna
Pascal J. Bourguignon p...@informatimago.com wrote:

 Alternatively, we could have:

 (defsystem :foo
:version-major 1
:version-minor 0
:version-release 42
:human-readable-version-string 1.0.gamma.XLII/pescadero:whasa)

 or:

 (defsystem :foo
:version (1 0 42)
:human-readable-version-string 1.0.gamma.XLII/pescadero:whasa)

  Actually, I had something like that in mind. With this idea of
  allowing individual systems to handle their own versioning logic, I
  intended to put something like '(1 3 :beta 4 Release Name) in the
  :version slot.

  A human-readable version is different from a version specifier. ASDF
  already does something shaky in this regard, even for its simplistic
  versioning scheme: because it normalizes versions into strings, it
  needs to provide UNPARSE-VERSION! Yuck.

  So if ASDF (or its users) insists on have human readable version
  strings, I wouldn't mind systems having both :version and
  :version-string.

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: The dictatorship of versioning

2015-06-16 Thread Didier Verna
Robert Goldman rpgold...@sift.net wrote:

 So what happens when the programmer updates the human readable version
 and not the canonical version, or vice versa?  Wouldn't it be better
 to functionally derive one of these two forms from the other?  E.g.,
 (defgeneric formatted-version (component version-spec))

  Probably. The only advantage I see in PB's suggestion is for people
  actually reading the system definition's code. But then, don't do
  that. Use Declt to create the reference manual ;-)

 I am also disinclined to add something like the proposed

  +1

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: The dictatorship of versioning

2015-06-16 Thread Didier Verna
Robert Goldman rpgold...@sift.net wrote:

 Now: a request for management purposes: Didier, would you be so kind
 as to describe the proposal (I think cut and paste out of your earlier
 emails would do admirably) in a ticket on launchpad.net?

  OK. I will also add Pascal's suggestion to have both a canonical and
  human readable version slot.

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: The dictatorship of versioning

2015-06-16 Thread Didier Verna
Robert Goldman rpgold...@sift.net wrote:

 Just to clarify: I am NOT saying Pascal is wrong to want these things
 or to do them himself.  And I AM saying that ASDF should make it
 possible for him to do so.

  ASDF could call FORMATTED-VERSION itself to initialize the
  corresponding slot (if any), and refrain from providing a writer for it.

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: The dictatorship of versioning

2015-06-16 Thread Didier Verna
Robert Goldman rpgold...@sift.net wrote:

 Why would that be a win over just calling FORMATTED-VERSION on demand?

 I.e., we could just provide something like

 (defgeneric FORMATTED-VERSION (C optional version)
   (:method ((COMPONENT C) optional version)
  (or version (component-version c)))

 and then the programmer could extend this as needed.

  You're right of course.

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



The dictatorship of versioning

2015-06-16 Thread Didier Verna

  Hi,

in general, I don't like the way ASDF tries to force you to comply with
its own design choices and policy. This is especially true for component
versioning. ASDF complains that it doesn't like my version numbers
(which, in fact, are not only numbers ;-), but I'm not ready to give up
on them. They're much more informative than ASDF's simplistic 1.2.3.

It seems that the only place ASDF uses our version numbers is in
VERSION-SATISFIES. There is also a VERSION-COMPATIBLE-P somewhere, but
it doesn't seem to be used. Fortunately, VERSION-SATISFIES is a generic
function, so I'm thinking I could work around it.

Not tested yet:
1. (defclass my-system-subclass (system) ())
2. (defsystem :foo.bar.baz :class 'my-system-subclass #|...|#)
3. (defmethod version-satisfies ((c my-system-subclass) version)
 #|my own version handling code|#)


Thoughts ? Will this be enough to satisfy ASDF ?

In an ideal world, the whole versioning API (version-satisfies, version
etc.) should have been implemented as proper component-based protocols...

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: The dictatorship of versioning

2015-06-16 Thread Didier Verna
I wrote:

 Thoughts ? Will this be enough to satisfy ASDF ?

  Not quite. I missed NORMALIZE-VERSION (ASDF attempting to be clever
  and doing all sorts of nasty DWIM stuff on version numbers).

  Attached patch would solve the problem, it seems. But then again, I
  don't really know what I'm doing. It wraps NORMALIZE-VERSION within a
  generic function which I can then specialize on my system, essentially
  bypassing normalization altogether, like this:

(defmethod asdf/parse-defsystem:normalize-component-version
((system my-system) form key pathname component parent)
  (declare (ignore pathname component parent))
  form)

diff --git a/parse-defsystem.lisp b/parse-defsystem.lisp
index e674e0c..ade94d7 100644
--- a/parse-defsystem.lisp
+++ b/parse-defsystem.lisp
@@ -10,6 +10,7 @@
   (:import-from :asdf/system #:depends-on #:weakly-depends-on)
   (:export
#:defsystem #:register-system-definition
+   #:normalize-component-version
#:class-for-type #:*default-component-class*
#:determine-system-directory #:parse-component-form
#:non-toplevel-system #:non-system-system
@@ -119,7 +120,11 @@
 (invalid
 (if-let (pv (parse-version v #'invalid-parse))
   (unparse-version pv)
-  (invalid))
+  (invalid)
+  (defgeneric* (normalize-component-version) (c form key pathname component parent)
+(:method (c form key pathname component parent)
+  (declare (ignore c))
+  (normalize-version form :pathname pathname :component component :parent parent
 
 
 ;;; inline methods
@@ -233,7 +238,7 @@ system names contained using COERCE-NAME. Return the result.
 (let ((sysfile (system-source-file (component-system component ;; requires the previous
   (when (and (typep component 'system) (not bspp))
 (setf (builtin-system-p component) (lisp-implementation-pathname-p sysfile)))
-  (setf version (normalize-version version :component name :parent parent :pathname sysfile)))
+  (setf version (normalize-component-version component version :component name :parent parent :pathname sysfile)))
 ;; Don't use the accessor: kluge to avoid upgrade issue on CCL 1.8.
 ;; A better fix is required.
 (setf (slot-value component 'version) version)

-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info


Re: The dictatorship of versioning

2015-06-16 Thread Didier Verna
Drake Wilson dr...@dasyatidae.net wrote:

 Curiosity: what _are_ your version numbers like, and how do you
 compare them?  It was a little too hard to find this readily from your
 website.  Maybe seeing a good example would help.

  A version specifier has a major and a minor number, a status (alpha,
beta, release candidate and patchlevel), a status number and a name. 

This is the beginning of the VERSION function in all my libraries:

(defun version (optional (type :number))
  Return the current version of Clon.
TYPE can be one of :number, :short or :long.

A version number is computed as major*1 + minor*100 + patchlevel, leaving
two digits for each level. Alpha, beta and rc status are ignored in version
numbers.

A short version is something like 1.3{a,b,rc}4, or 1.3.4 for patchlevel.
Alpha, beta or rc levels start at 1. Patchlevels start at 0 but are ignored
in the output, so that 1.3.0 appears as just 1.3.

A long version is something like
1.3 {alpha,beta,release candidate,patchlevel} 4 \Michael Brecker\. As for
the short version, a patchlevel of 0 is ignored in the output.


-- 
My new Jazz CD entitled Roots and Leaves is out!
Check it out: http://didierverna.com/records/roots-and-leaves.php

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: [asdf-devel] About some new system slots

2013-07-08 Thread Didier Verna
Faré fah...@gmail.com wrote:

 Although, it isn't clear yet how source-control may or may not specify
 the VCS used: should we prefix the URL with a git: or svn: or darcs:
 or some such? ASDF uses: :source-control (:git
 git://common-lisp.net/projects/asdf/asdf.git)

  Personally, I would not complicate this slot and just go for a simple
  URL pointing to a VCS related web page. If you start specifying more
  information there, you will end up with a big mess (which VCS, which
  access backend, which access type (r/o r/w) etc.).

That's just me of course.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: [asdf-devel] About some new system slots

2013-07-08 Thread Didier Verna
Robert Goldman rpgold...@sift.info wrote:

 The advantage of having the pair, of course, is that a simple URL does
 not necessarily identify the form of VCS.

  But what would be the use for this information? I mean, having this
  information as part of the system desciption.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



[asdf-devel] About some new system slots

2013-07-05 Thread Didier Verna

  Hello,

what's the purpose of the LONG-NAME slot in ASDF 3's system class?
Also, can I assume that HOMEPAGE, SOURCE-CONTROL and BUG-TRACKER are
meant to be URL strings ?

Thanks.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: [asdf-devel] component-load-dependencies

2013-06-27 Thread Didier Verna
Faré fah...@gmail.com wrote:

 since you provide no justification for what you are trying to do,
 anything can be reasonable or not.

  I'm not sure what I need to justify, since my original question was
  actually quite precise.


 My bet is that this isn't what you really want in the end, 

 Usually, one wants to get a list of components within a system.
 Then, one typically uses required-components, e.g. like this (YMMV):

  That's the opposite of what I want.

  Thank you very much, but even assuming I don't know what I want and
  you know what I want better than I know what I want, I'm still sure
  that I don't want the opposite of what I want.


 Have fun playing with ASDF.

  Not really, no.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



[asdf-devel] component-load-dependencies

2013-06-26 Thread Didier Verna

  Hello,

currently Declt advertises component dependencies by using
COMPONENT-LOAD-DEPENDENCIES. This function however only returns a list
of symbols naming the components.

What would be the best way to retrieve a list of component objects
instead ?

Thanks!

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: [asdf-devel] component-load-dependencies

2013-06-26 Thread Didier Verna
Faré fah...@gmail.com wrote:

 what are you *really* trying to do?

  Really, trying to get the same thing that component-load-dependencies
  gives me, but as component objects instead of names.


 Usually, one wants to get a list of components within a system.
 Then, one typically uses required-components, e.g. like this (YMMV):
   (asdf:required-components (asdf:find-system :fare-utils)
 :component-type '(not asdf:system) :keep-operation 'asdf:load-op
 :keep-component 'asdf:source-file)

  That's the opposite of what I want. It seems that
  component-load-dependencies gets me all the (direct) things a
  component depends on (for loading). That may be implicit in an ASDF
  system description if :serial t is used, or explicit with a :depend-on
  declaration. This is exactly what I want, but as objects, not names.


 If you *really* want to walk the dependencies by yourself, use
 asdf/plan:visit-dependencies.  There are also functions
 map-direct-dependencies, reduce-direct-dependencies,
 direct-dependencies that you may want to use instead. More often than
 not, it's a bad idea, though.  Most of the time, if you need to go
 under the hood, it is better to manually use traverse-action
 traverse-actions traverse-sub-actions with your choice of plan, e.g. a
 sequential-plan or filtered-sequential-plan.

  All of this is way beyond me.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: [asdf-devel] component-load-dependencies

2013-06-26 Thread Didier Verna
I wrote:

   All of this is way beyond me.

  But by looking at the code, it seems that the dependency names I'm
  looking for are in the SIDEWAY-DEPENDENCIES slot of the
  components. From there, it seems that I can use
  RESOLVE-DEPENDENCY-NAME to finally get a component object.

Does this sound reasonable?

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



[asdf-devel] Cannot use latest git ECL (asdf/quicklisp are involved)

2013-06-24 Thread Didier Verna

  Yothere,

I upgraded ECL this morning to the latest repo version and I cannot use
it anymore with my usual setup (-norc works). My local versions of
Quicklisp and ASDF are also the lastest.  I have this in my init file:

;; Do ASDF first (when a compiler provides it directly, I think it is better
;; to use its version than mine).
(require :asdf
 #-(or sbcl cmu ccl ecl mkcl xcl allegro
   (and lispworks (not lispworks-personal-edition)))
 '(#p/usr/local/share/common-lisp/source/asdf/build/asdf.lisp))

#-quicklisp
(let ((quicklisp-init
   /usr/local/share/common-lisp/source/quicklisp/setup.lisp))
  (when (probe-file quicklisp-init)
(load quicklisp-init)))



With this configuration, running ECL on the command-line gives me this:

didier(pts/4)% ecl Err 1 11:27 06/24/13
;;; Loading #P/home/didier/.clrc
;;; Loading #P/usr/local/lib/ecl-12.7.1/asdf.fas
;;; Loading #P/usr/local/lib/ecl-12.7.1/cmp.fas
;;; Loading /usr/local/share/common-lisp/source/quicklisp/setup.lisp
ASDF could not load sockets because Error while trying to load definition for 
system sockets from pathname /usr/local/lib/ecl-12.7.1/sockets.asd: No 
applicable method for SOURCE-FILE-TYPE with arguments of types
 COMPILED-FILE
 PREBUILT-SYSTEM.
;;; Error:
;;;   in file impl.lisp, position 7644
;;;   at (DEFINE-IMPLEMENTATION-PACKAGE ECL ...)
;;;   * The form (REQUIRE 'SOCKETS) was not evaluated successfully.
;;; Error detected:
;;; Error while trying to load definition for system sockets from pathname 
/usr/local/lib/ecl-12.7.1/sockets.asd: No applicable method for 
ASDF:SOURCE-FILE-TYPE with arguments of types
;;;  COMPILED-FILE
;;;  PREBUILT-SYSTEMAn error occurred during initialization:
Error while invoking #compile-op (:VERBOSE NIL) 0b0e79a8 on
#cl-source-file quicklisp impl.
zsh: exit 1 ecl



I see that ELC's version of ASDF is old, so I tried to load ASDF 3 by
removing 'ecl from the #-() form above. Now I get this instead:

didier(pts/4)% ecl Err 1 11:27 06/24/13
;;; Loading #P/home/didier/.clrc
;;; Loading /usr/local/share/common-lisp/source/asdf/build/asdf.lisp
An error occurred during initialization:
Cannot delete the directory 
#P/home/didier/.cache/common-lisp/ecl-12.7.1-52ca46e0-linux-x86/usr/local/share/common-lisp/source/asdf/build/asdf.fas.
C library explanation: No such file or directory..
zsh: exit 1 ecl


Any advice ?

Thanks.

-- 
Resistance is futile. You will be jazzimilated.

Lisp, Jazz, Aïkido: http://www.didierverna.info



Re: [asdf-devel] ASDF 2.26 in Quicklisp

2012-11-29 Thread Didier Verna
Robert Goldman rpgold...@sift.info wrote:

 Thanks.  If I get some downtime, I'll try to either split these
 subsections into nodes (if anyone has an emacs command that will do
 that automagically, please LMK), or add anchors.

  You may want to start with C-x h C-u M-x texinfo-insert-node-lines.
This will create all missing nodes for every sectionning command and
fill them up with the proper title. However, you will most probably need
to update the structure afterwards.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel


Re: [asdf-devel] ASDF 2.26 in Quicklisp

2012-11-28 Thread Didier Verna
rpgold...@sift.info wrote:

 As far as I can tell, this is a misfeature of texinfo. The links only
 work to the node level (at least in the info browser). So we would
 need to reactor the document into smaller nodes to fix that.

  That's not really a misfeature. That fact is that Texinfo uses nodes
  as its primary sectionning mechanism. You need to think in terms of
  node first when you write Texinfo. Every sectionning command that you
  use should be associated with a node, and every node that has
  sub-nodes should have a menu. It seems that you only have nodes for
  chapters, which explains the shaky TOC.

 Unfortunately, in addition to requiring some work, that would also
 give us a document with very small pages, that would be a nuisance
 when attempting to read in chunks (as opposed to jumping to a very
 specific item).

  That is correct, although I don't find that this is such a nuisance,
  since you have all the hyperlinks you want. Otherwise, what you can do
  is generate a single web page for the whole doc (Cf. --no-split).

  What I do find missing from Makeinfo is a --split-level option instead
  of the --no-split one. It would be nice if, for instance, we could
  specify that we want to split at the chapters level only.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel


[asdf-devel] Using asdf with Corman Lisp 3

2012-09-11 Thread Didier Verna

  Hello,

I'm trying to use ASDF (git repo) with Corman Lisp 3.0 natively on
Windows. I managed to have Corman Lisp load ASDF, but now I have a
configuration problem.

I have a file C:\Users\Didier\.config\common-lisp\source-registry.conf
which contains this:

(:source-registry
  (:tree C:\Program Files (x86)\Common Files\Common Lisp\)
  :inherit-configuration)

But ASDF doesn't find any of the packages I put there.
asdf::*source-registry* seems to be NIL. What am I doing wrong ?


Thanks !

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel


Re: [asdf-devel] asdf 2.23, and contribs

2012-07-05 Thread Didier Verna
Faré fah...@gmail.com wrote:

 Speaking of which, some time ago, I started to collect asdf
 extensions, and I just added a listing of them on the asdf webpage. 
 Please suggest more extensions that I may list on the page.

  ASDF-FLV, related to CDR #9.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel


[asdf-devel] Status of :feature

2011-03-23 Thread Didier Verna

  Hello,

what is the current status of :feature in a list of dependencies? I
mean, is it safe to replace #+ reader conditionals in the asd file with
it?

Thanks.

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel


Re: [asdf-devel] ASDF 2 questions

2010-09-30 Thread Didier Verna
I wrote:

 [ Please, Cc: me as I'm not on the mailing list ]

here's another one:

In ASDF 1, (component-pathname (find-system ...)) returned the system's
*directory*, which was coherent because the system is a module, so its
pathname is a directory just like for any other sub-module.

In ASDF 2, it seems to return the .asd file instead.
Is this intentional ?

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel


Re: [asdf-devel] ASDF 2 questions

2010-09-30 Thread Didier Verna
Faré fah...@gmail.com wrote:

 5/ Finally, I would like confirmation that ASDF now handles outdated
   fasl's correctly, and we don't need to do the black magick
 ourselves.

 I'm not sure what you mean, so I'd say probably not. If you have
 black magick that you think should be part of ASDF, please submit it
 here, and/or as an ASDF bug on launchpad.

  Sorry for being too vague. For ASDF 1, I had a plug to automatically
recompile outdated fasls (I probably found it on the internet years ago;
don't remember):

(defmethod asdf:perform :around
((o asdf:load-op) (c asdf:cl-source-file))
  (handler-case (call-next-method o c)
(#+sbcl sb-ext:invalid-fasl
#+cmu ext:invalid-fasl
#+allegro excl::file-incompatible-fasl-error
#+lispworks conditions:fasl-error
#-(or sbcl cmu allegro lispworks) error
()
(asdf:perform (make-instance 'asdf:compile-op) c)
(call-next-method

... and I was wondering if ASDF 2 did something like this on its own.


Thanks !

-- 
Resistance is futile. You will be jazzimilated.

Scientific site:   http://www.lrde.epita.fr/~didier
Music (Jazz) site: http://www.didierverna.com

___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel