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

[asdf-devel] bug in new ASDF
by Robert Goldman 13 Jul '09

13 Jul '09

I see the following when I try to load an asdf system now: Error loading #P"/Users/rpg/clinit.cl": While searching for system `asdf-context`: `(MERGE-PATHNAMES systems/ /Users/rpg/lisp/asdf-install-systems/)` evaluated to `/Users/rpg/lisp/asdf-install-systems/systems/` which is not a directory. The problem with this error is that, in fact, that IS a directory: CL-USER(2): (probe-file "/Users/rpg/lisp/asdf-install-systems/systems/") #P"/Users/rpg/lisp/asdf-install-systems/systems/" I'm looking in sysdef-central-registry-search and the logic seems to be completely borked. It looks for a system definition and, if it doesn't find one, it assumes that the directory name is bad. I believe the logic should be: 1. Look at the directory and ensure that it exists. 2. If it does not exist, push it onto the bad list 3. Else merge in the system name and look for the system definition. The current logic merges in the system name first, so misdiagnoses. [I will now proceed to wrestle with git, which I am coming to loathe with a consuming hatred, in order to attempt to verify that my diagnosis is correct, and then send a patch. More soon.]

4 12

Re: [asdf-devel] asdf 1.354 ?
by Gary King 12 Jul '09

12 Jul '09

(cc'd to list) Hi Faré, My bad. I forgot that I had been working in a branch so my push of master didn't push out the new changes. I just fixed this and pushed a moment ago. Please let me know if your mileage still varies. On Jul 11, 2009, at 5:24 PM, Faré wrote: > 2009/7/11 Gary King <gwking(a)metabang.com>: >> You may be going crazy but your sighting of the 1.354 message isn't >> evidence >> for that possibility. >> >> I did send such a message earlier today. >> >>> http://www.mail-archive.com/asdf-devel@common-lisp.net/msg00057.html >> > Dear Gary, > > thanks for your answer. I can't see it on git, though. Did you commit > to cvs, and then a daemon will update git, or something? > http://common-lisp.net/project/asdf/asdf.git > > I wanted to update xcvb to use this "official" (I think) git repo as > asdf upstream instead of xcvb's own thingie, but I can't find asdf > 1.354 there. > > [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org > ] > A co-mathematician is a machine for converting cotheorems into fee. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

2 1

[asdf-devel] Patch for ACL 8.0
by Jeff Palmucci 11 Jul '09

11 Jul '09

When loading the git version of asdf under ACL 8.0, you get the following worrying message: Warning: Nested reader conditional detected on #<FILE-SIMPLE-STREAM #P"/afs/csail.mit.edu/u/j/jpalmucci/repo-install/repo- install/../asdf/asdf.lisp" for input pos 52418>. The behavior of this feature of ACL changed between ACL 7.0 and 8.0 to be more in line with the intent of the ANS specification. You should examine the code in question to make sure it does what you intend. In ACL 8.0, (list #+allegro :allegro #-allegro #+foo :foo #-foo :default) evaluates to (:allegro) instead of (:allegro :default) as in ACL 7.0 and before. See the documentation for EXCL:*WARN-ON-NESTED-READER-CONDITIONALS* and EXCL:*SHARP-PLUS-DE-FACTO-STANDARD-COMPATIBLE* for more information. Here as a patch to fix the problem.

2 1

[asdf-devel] Guard against (push "/foo/bar" asdf:*central-registry*)
by Tobias C. Rittweiler 11 Jul '09

11 Jul '09

I think it's bitten pretty much all of us that we at least once tried to push a non-directory-designating filename to *CENTRAL-REGISTRY*. It's a common pitfalls for newcomers. Couldn't ASDF signal a warning when it encounters such a thing while grovelling through the registry? -T.

7 15

[asdf-devel] pushed version 1.354
by Gary King 11 Jul '09

11 Jul '09

I did not move the RELEASE or STABLE tags though... Sat, 11 Jul 2009 13:15:53 -0400 Gary King handle bad *central-registry* itmes; xcvb compat * Add two restarts (coerce-entry-to-directory and remove-entry-from- registry) and use them to guard against *central-registry* entries that are not directories. * add some XCVB goodness to aid in compatibility. Thu, 9 Jul 2009 12:05:31 -0400 Gary King Patch for XCVB compatibility from Fare -- 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] Fwd: can't compile-file then load asdf.lisp
by Faré 09 Jul '09

09 Jul '09

Apparently, it is incorrect to try to update ASDF from a system where an older version of ASDF has already been loaded from which some DEFUNs (e.g. SYSTEM-SOURCE-FILE) have since converted to DEFGENERICs. This means that if you have an old clisp from debian and try to use the newer ASDF, you're out of luck. As a remedy, could we prepend the defpackage in asdf.lisp with the following? (eval-when (:compile-toplevel :load-toplevel) (let ((package (find-package '#:asdf))) (when package (delete-package package)))) [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Instead of loving your enemies, treat your friends a little better. -- Edgar Watson Howe ---------- Forwarded message ---------- From: Sam Steingold <sds(a)gnu.org> Date: 2009/7/8 Subject: Re: can't compile-file then load asdf.lisp To: Faré <fahree(a)gmail.com> Cc: clisp-list(a)lists.sourceforge.net Faré wrote: > > If I grab the latest asdf.lisp from git and try to compile-file it the one I have comes from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/cclan/asdf/ and it compiles and loads just fine. > then load it, I get a weird error message. > > WARNING: DEFGENERIC: redefining function SYSTEM-SOURCE-FILE in > /dev/shm/tmp/fare/xcvb-0.320/dependencies/asdf/asdf.fas, was > defined in top-level > *** - ENSURE-GENERIC-FUNCTION: SYSTEM-SOURCE-FILE does not name a > generic function this means that you have defined a regular function (with DEFUN) and now are trying to redefine it with DEFGENERIC. since asdf.lisp does not do that, you, apparently, have this function defined somewhere else.

3 4

[asdf-devel] Making ASDF ready for XCVB.
by Faré 08 Jul '09

08 Jul '09

Dear ASDF maintainers, would it be OK to apply the attached diff to asdf in git? It creates a trivial build.xcvb and a trivial module definition for ASDF, so that ASDF can be included in builds that use XCVB (including a bootstrapped version of XCVB itself). [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] If all values are relative, then cannibalism is a matter of taste. -- Leo Strauss

1 0