asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[asdf-devel] announce : 1.357
by Gary King 12 Aug '09

12 Aug '09

(small steps forward!) test-op depends on load-op (thanks to rpgoldman(a)sift.info) * Improve error message for bad dependencies * New default is for test-op to depend on load-op * tweak run-program for SBCL so that ACL isn't #+no #+no bothered * tweak write-test-web-page and write-license * tweak some tests Thanks Robert, et. al. for good discussion, etc. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

Re: [asdf-devel] About regression tests and libraries
by Tobias C. Rittweiler 12 Aug '09

12 Aug '09

Juan Jose Garcia-Ripoll writes: > What I would like to ask CL developers is to begin shipping regression > tests with their libraries, and perhaps agree on an standard so that > one can programatically check whether a library builds or not. This > feature could be even included in ASDF, asdf-install, etc, just like > "make check" is now a de-facto standad in Autoconf. There's (ASDF:OOS 'ASDF:TEST-OP <system>), and on very recent revisions even (ASDF:TEST-SYSTEM <system>) as an abbeviation. I don't think this has been properly documented in the manual of ASDF yet. I hence CC'd the asdf-devel mailing list so this will hopefully get promoted with the due it deserves. -T.

7 20

[asdf-devel] version numbers
by Daniel Herring 07 Aug '09

07 Aug '09

ASDF has a poorly-defined versioning system. I thought the following link may be of general interest. http://www.dagolden.com/index.php/369/version-numbers-should-be-boring/ There sure are many ways to mess this up. I'm not convinced there are any ways to not mess it up. Related links http://www.gnu.org/software/libtool/manual/html_node/Libtool-versioning.html http://stackoverflow.com/questions/663209/can-someone-explain-about-linux-l… http://www.linux.com/archive/feature/45507?theme=print Given the way ASDF is used today and the rapidly changing ABI of many CL implementations, binary compatibility is a nonexistant issue. Today's CL cares rather about compile-time compatibility. Either way, I almost think the correct solution is to say - each library release will have a unique version number - each library release will have a list of old version numbers for which it is upwards compatible - each dependent library or application will list which versions it was developed for - the "linker" (require or asdf) selects the newest version compatible with the version specified by the dependent This is similar to the libtool scheme, but using general data structures rather than trying to encode everything into the filename. How would asdf respond to two files named X.asd? It doesn't scan all such files looking for the most recent version, does it? (end rambling) - Daniel

2 1

[asdf-devel] Three queries ..
by Greg Bennett 05 Aug '09

05 Aug '09

Good afternoon from Greg Bennett. I am trying to convert some mk-defsystem files to asdf and find myself a bit stuck over source and output files, as well as over asdf conventions about the case of certain text items. My mk-defsystem files contain the two keywords :source-pathname and :binary-pathname As far as I can see, :pathname in asdf plays the role of :source-pathname. In looking for examples, I found the following in the mcclim.asd file: .. ((:module "Tests" :pathname #.(make-pathname :directory '(:relative "Drei" "Tests")) :components .. And indeed there is a subdirectory Tests of the directory Drei which is in the right place relative to the opening directory of the .asd file for :relative to make sense. Q1: Is it possible/permitted to say things like: '(:relative "One" "Two" "Three") to have asdf look two subdirectories down the tree ? I have been unable to find examples of the use of :output-files in asdf. This option seems to provide the role of :binary-pathname in mk-defsystem. Currently, all tour project's binary files are stored in their own tree with its own root but with the structure of the source tree maintained. Q2: Does the syntax of :output-files permit this sort of thing ? I would seem to need a statement of the form #.(make-pathname :directory '(:absolute "Whatever")) since this is a separately rooted tree. Unless I find a positive answer to Q1, in which case, presumably the syntax of :output-files will be similar and I can locate the driving .asd file high enough up in the whole project for everything to be relative. From the code (above) I cut from mcclim.asd it seems that mixed case pathnames are allowed. Q3: Have I misunderstood the on-line manual here ? In discussing components it seems insistent on lower case, which I had assumed asdf would 'demand' everywhere. Thanks for any and all assistance and insights, Cheers /Greg Bennett

3 2

[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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel