July 2009 - asdf-devel - mailman3.common-lisp.net

[asdf-devel] recursiveness of :FORCE
by Tobias C. Rittweiler 09 Nov '09

09 Nov '09

When I use :FORCE, in most cases I do want to recompile solely the specified system, not all its dependencies. In my ideal world, :FORCE T would recompile the specified system only, and :FORCE :ALL would recompile it along its dependencies. Of course that would be backwards-incompatible, so perhaps better stick with the current behaviour for :FORCE T, but add :FORCE :SYSTEM, or :FORCE :SHALLOW, or similiar. -T.

2 5

[asdf-devel] patch system-source-file
by Greg Pfeil 25 Sep '09

25 Sep '09

Here are a couple changes to ASDF that I made in the process of creating an ASDF browser for CCL's IDE: • system-source-file now works for systems without their own .asd • optional parts of systems (version, maintainer, etc.) don't leave their slots unbound

7 17

[asdf-devel] announce: 1.356
by Gary King 21 Jul '09

21 Jul '09

> Tue, 21 Jul 2009 13:39:33 -0400 > Gary King > fix my bad in `directory-pathname-p` > * Patch from Joyce Chen for a braindead directory-pathname-p error > on my part * remove debugging statement in check-component-input and documentation improvements... -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

[asdf-devel] Small fixup of bogus function in directory-pathname-p
by Joyce Chen 21 Jul '09

21 Jul '09

Fare's small fixup of bogus function in directory-pathname-p. ccl complained about x not being used. I don't have commit privileges, so if someone could kindly review the change and commit it :) Thanks, Joyce diff --git a/asdf.lisp b/asdf.lisp index 1e1118d..714c529 100644 --- a/asdf.lisp +++ b/asdf.lisp @@ -448,12 +448,11 @@ ways that the filename components can be missing are for i Note that this does _not_ check to see that `pathname` points to an actually-existing directory." - (let ((null-components (list nil :unspecific ""))) - (flet ((check-one (x) - (not (null (member (pathname-name pathname) null-components - :test 'equal))))) + (flet ((check-one (x) + (member x '(nil :unspecific "") :test 'equal))) (and (check-one (pathname-name pathname)) - (check-one (pathname-type pathname)))))) + (check-one (pathname-type pathname)) + t))) #+(or) ;;test

2 1

Re: [asdf-devel] [cclan-list] How to depend on a system optionally?
by Nikodemus Siivola 21 Jul '09

21 Jul '09

2009/5/18 Robert Goldman <rpgoldman(a)sift.info>: > Tobias C. Rittweiler wrote: >> I've read several times that it's a head ache to configure optional >> dependencies with ASDF. >> >> How true is that? Could we perhaps provide another clause >> :OPTIONALLY-DEPEND-ON in DEFSYSTEM which would load a system only if >> available? Doesn't :WEAKLY-DEPENDS-ON do what you want? Cheers, -- Nikodemus

4 14

[asdf-devel] Partial patch for ASDF manual
by Robert Goldman 20 Jul '09

20 Jul '09

The existing manual doesn't document ASDF's :weakly-depends-on, an issue which this patch addresses. Two notes about this patch, which characterize it as interim: 1. It would help if I had a better example of the use of :weakly-depends-on. I believe I have the semantics right, but I don't have a good use case (a simple textual discussion is enough of a use case). It's not so much how to use the feature as how people write systems that use the feature. For example, would you write a piece of code that weakly depended on system foo, set up system foo so that it pushed :foo on the *features* and then sprinkle "#+ foo" around your code? It almost seems like we'd want a corresponding construct that would load a file only if some feature was present at system operate time (NOT at the time when the ASDF system definition was read). 2. I found that documenting this exposed a weakness in the ASDF manual's structure. The manual provides a section that documents the grammar, and a section that documents the ASDF object model. There isn't really a section that gives a semantic counterpart to the syntax. One might think that the object model documentation would fill this need, but it doesn't really. :weakly-depends-on is a good example of this hole, because weakly-depends-on is translated either into a component dependency or into nothing, so it has meaning only as part of a defsystem form. We can't describe its semantics in the section on the object model, because there is no object model component that corresponds directly to the weakly-depends-on argument. BTW, line 1319 of asdf.lisp seems to be someone's debugging statement left around. Shouldn't it be excised? diff --git a/asdf.texinfo b/asdf.texinfo index cfef5c6..0d26235 100644 --- a/asdf.texinfo +++ b/asdf.texinfo @@ -338,6 +338,7 @@ option := :components component-list | :output-files method-form | :operation-done-p method-form | :depends-on ( {dependency-def}* ) + | :weakly-depends-on ( {dependency-def}* ) | :serial [ t | nil ] | :in-order-to ( {dependency}+ ) @@ -381,6 +382,30 @@ is equivalent to (:file "c" :depends-on ("a" "b"))) @end lisp +@subsection Weakly-depends-on + +The @code{weakly-depends-on} argument says of the component depended on +``if this component can be found, then impose a dependency, otherwise +ignore it.'' At the top level, this can be useful for allowing a system +to take advantage of another system, if it is present. For example, a +system might generate on-line documentation if a documentation +generation system (like TINAA, Albert, etc.) was present. A system that +does text matching might do only simple matching but weakly depend on a +regular expression system and, if that system is installed, would be +able to also do regular expression matching. + +Notes: +@itemize +@item +It's not entirely clear to me that this option is very helpful at a +level below the top-level. Since it uses find-component, the behavior +differs between top level and lower level; perhaps that needs to be +explained. +@item +Presumably this will be most useful when complemented by some +conditional loading construct in the system that has the dependency. +What is that construct? +@end itemize @subsection Source location

3 3

[asdf-devel] Problem with pathnames with name component = ""
by Robert Goldman 20 Jul '09

20 Jul '09

I have found out how this problem has seeped into ASDF --- ASDF-INSTALL, at least the version I have (I am checking now to see if there's an improved version) --- seeds asdf:*central-registry* with pathnames with :name = "". This is done by the directorify function in installer.lisp. Investigating further. Perhaps this behavior should simply be stamped out of ASDF-install....

1 1

[asdf-devel] added gitweb access (at last)!
by Gary King 18 Jul '09

18 Jul '09

I just added the sauce to let cl.net's gitweb find ASDF's project. See http://common-lisp.net/gitweb?p=projects/asdf/asdf.git;a=summary and let me know if anything is amiss. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

[asdf-devel] Apply *read-default-float-format* to lisp files
by Brett van de Sande 17 Jul '09

17 Jul '09

I have some lisp source files that contain some (many) floating point numbers. How can I use asdf to ensure these files are read using (setf *read-default-float-format* 'double-float) without setting *read-default-float-format* globally? Thanks, BvdS

3 2

[asdf-devel] pushed 1.355
by Gary King 16 Jul '09

16 Jul '09

Includes changes to directory-pathname-p; and various other foo-faw. Wed, 15 Jul 2009 12:37:49 -0400 Gary King fixed minor glitches in test result web page generation Wed, 15 Jul 2009 10:22:10 -0400 Gary King improve `directory-pathname-p` * After much discussion, here's another attempt at `directory-pathname- p`. * make sure we push when we `make archive` Wed, 15 Jul 2009 10:17:39 -0400 Gary King (for real this time) modest make improvements * extract LICENSE file out of asdf.lisp directly (DRY wins) * make `make-temporary-package` more mixed-case friendly -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0