asdf-devel February 2010

asdf-devel@common-lisp.net

17 participants
39 discussions

[asdf-devel] LispWorks fix
by Chun Tian (binghe) 04 Feb '10

04 Feb '10

Hi, ASDF I found a typo in LispWorks support code which stops ASDF compiling: diff --git a/asdf.lisp b/asdf.lisp index 3c5dbbd..ad97554 100644 --- a/asdf.lisp +++ b/asdf.lisp @@ -438,7 +438,7 @@ and NIL NAME and TYPE components" ;;; what about VERSION??? #+cmu (cdr (assoc (intern x :keyword) ext:*environment-list*)) #+lispworks - (lispworks:environment-xiable x) + (lispworks:environment-variable x) #+allegro (sys:getenv x) #+gcl Please fix it. --binghe

2 1

[asdf-devel] A dream for ASDF2
by Daniel Herring 04 Feb '10

04 Feb '10

Tobias C. Rittweiler wrote: Re: [asdf-devel] Is this necessary in this form? Re: ASDF 1.501 > Isn't asdf-output-locations somewhat like a CL pendant to `make install' > if you squint your eyes? > > Shouldn't that be an integral part of ASDF? Exactly yes and absolutely no. Not necessarily in that order. My issue is that there is a great similarity; this similarity is driven by a need inherent in the use of libraries; but ASDF (due to history) has certain things absolutely backwards. There are many users that a build system must support. - developers do incremental compiles - maintainer creates a release (collect sources, build docs, etc. into a self-contained archive) - maintainer checks that the release actually builds, cleans, installs, etc. - user or system integrator configures the release for local needs - the release is compiled (often into a separate directory or on a separate computer) - the release is tested (before install) - the release is installed (often to a read-only space, as root, or into a temporary directory that will be archived for distribution) - the release is loaded (often without sources) - the release is uninstalled ASDF needs a coherent story for the person doing each of these jobs. Instead, the current model lumps most everything into a single "load-op", and there is no principled way to perform or configure each of the above phases separately. My biggest concern with the recent changes is that they build a big scaffold that institutionalizes a design in need of fundamental changes. Some parts of .asd files may need incompatible changes; but I think most uses are completely upgradeable. However, I do not think the recent ASDF proposals will be. I would like the ASDF architecture to look something like - bootstrap a few (self-contained) core utils using a special install sequence (simple COMPILE, test, and install scripts) - ASDF uses LOAD to pull these in; as each loads, more functionality becomes available (aka SBCL boostrap). - All other packages can now be built with the full ASDF. - (optional) ASDF may upgrade itself without the bootstrap sequence. ASDF features I would like: - Standard way to pass configuration options to ASDF for building a specific system. For example, ASDF should let me configure which compression backend cl-pdf uses, and ASDF should write these choices to file for me. This should be a replayable config file that can be modified for reconfiguration, or read in for compilation and install. I should be able to have several builds at once, each with a different set of choices. - Standard options for each system. For example, a popular one might allow ASDF to autorecompile fasls when the sources change. Another would be an install prefix. Another is to modify the installed system name (e.g. add version info; asdf-1.5 would load the ASDF package, version 1.5). Another to enable the system config cache (below). - Generic configuration cache, independent of use. In other words, a simple configuration format where I can set key/value pairs. Some of which may happen to control ASDF source locations, others may control ASDF output locations, yet others may be defined by end-user ASDF files. This cache should have three levels, one for the sysadmin, one for the user, and one for inside the system configuration area (usually the source tree). Compare the autoconf site configuration mechanism. http://www.gnu.org/software/autoconf/manual/html_node/Site-Configuration.ht… - ASDF compile/install spits out a system.fasl. Semantically, loading this causes the entire library to be loaded. On some CL's, it might simply be the concatenation of the compiled source files; on others, it might LOAD them all in order. The above is a long-enough list for today. I think it covers most of the bases. These things aren't problems I'm creating; they are lessons I have gleaned from GNU autotools and other build systems. Whenever ASDF takes a shortcut, we have issues. For example, "" # We still need to find a way to precompile libraries # Because asdf is now taking care of placing the fasl file in the correct place, we cannot remove fasls for a specific implementation or library, so we nuke them all. Not optimal. "" - http://pvaneynd.livejournal.com/133491.html These are part of the standard autotools procedure; they represent a couple use cases from the first list above. Later, Daniel P.S. Here's a draft response I penned for an earlier post Subject: Re: [asdf-devel] ASDF 1.501 > Next, comes a similar revamp of ASDF-BINARY-LOCATIONS configuration. > Or maybe a wholesale replacement of ABL with something that's simpler > and configured in a way similar to source-registry? What do YOU think? What do I really think? Its great that ASDF is getting some TLC, but the whole "register the sources" thing is fundamentally flawed. >From the end-user's perspective, the whole purpose of a "defsystem" (henceforth library loader) is to get one or more packages into the running lisp.

3 3

[asdf-devel] Two patches in passing
by Robert Goldman 04 Feb '10

04 Feb '10

I found some cases where the tests could go bad. One where the tests could fail to find asdf.fasl (or equivalent) and one where a style-warning in SBCL could cause the tests to fail. Those are the two messages that should be coming through. I'm not fully sure how to use git send-email yet....

1 0

[asdf-devel] [PATCH] Fix for launchpad bug 516794.
by rpgoldman＠sift.info 04 Feb '10

04 Feb '10

From: Robert P. Goldman <rpgoldman(a)real-time.com> There was code here that caused a style warning because it was checking for the return of safe-file-write-date being NIL, which it could never be. This indicated odd treatment of missing file write dates in operation-done-p. I have revised this. --- asdf.lisp | 55 +++++++++++++++++++++++++------------------------------ 1 files changed, 25 insertions(+), 30 deletions(-) diff --git a/asdf.lisp b/asdf.lisp index 39160ee..edd2d66 100644 --- a/asdf.lisp +++ b/asdf.lisp @@ -799,7 +799,11 @@ to `~a` which is not a directory.~@:>" ;; that's the case, well, that's not good, but as long as ;; the operation is otherwise considered to be done we ;; could continue and survive. - (or (file-write-date pathname) 0)) + (or (file-write-date pathname) + (progn + (warn "Missing FILE-WRITE-DATE for ~S: treating it as zero." + pathname) + 0))) (defun find-system (name &optional (error-p t)) (let* ((name (coerce-name name)) @@ -992,35 +996,26 @@ to `~a` which is not a directory.~@:>" (defmethod input-files ((operation operation) (c module)) nil) (defmethod operation-done-p ((o operation) (c component)) - (flet ((fwd-or-return-t (file) - (let ((date (safe-file-write-date file))) - (cond - (date) - (t - (warn "~@<Missing FILE-WRITE-DATE for ~S: treating ~ - operation ~S on component ~S as done.~@:>" - file o c) - (return-from operation-done-p t)))))) - (let ((out-files (output-files o c)) - (in-files (input-files o c))) - (cond ((and (not in-files) (not out-files)) - ;; arbitrary decision: an operation that uses nothing to - ;; produce nothing probably isn't doing much - t) - ((not out-files) - (let ((op-done - (gethash (type-of o) - (component-operation-times c)))) - (and op-done - (>= op-done - (apply #'max - (mapcar #'fwd-or-return-t in-files)))))) - ((not in-files) nil) - (t - (and - (every #'probe-file out-files) - (> (apply #'min (mapcar #'safe-file-write-date out-files)) - (apply #'max (mapcar #'fwd-or-return-t in-files))))))))) + (let ((out-files (output-files o c)) + (in-files (input-files o c))) + (cond ((and (not in-files) (not out-files)) + ;; arbitrary decision: an operation that uses nothing to + ;; produce nothing probably isn't doing much + t) + ((not out-files) + (let ((op-done + (gethash (type-of o) + (component-operation-times c)))) + (and op-done + (>= op-done + (apply #'max + (mapcar #'safe-file-write-date in-files)))))) + ((not in-files) nil) + (t + (and + (every #'probe-file out-files) + (> (apply #'min (mapcar #'safe-file-write-date out-files)) + (apply #'max (mapcar #'safe-file-write-date in-files)))))))) ;;; So you look at this code and think "why isn't it a bunch of ;;; methods". And the answer is, because standard method combination -- 1.6.5.3

1 0

[asdf-devel] Dependency issues with module sub-class
by Scott Bell 03 Feb '10

03 Feb '10

Hi folks, Recently, in order to increase the modularity of our project's ASDF dependencies, I introduced a sub-class of MODULE called GROUP. We wanted to keep all of our main .lisp files in the toplevel, so the purpose of the class is simply to define a method for the COMPONENT-RELATIVE_PATHNAME generic function. The problem that I'm experiencing is that the dependencies at the MODULE (GROUP) level don't appear to be established (i.e. modifying one group does not cause its dependents to be re-compiled). Here is a snippet of the code: ;; a GROUP is an ASDF component whose files are located in its parent ;; component's directory. (defclass group (module) ()) (defmethod component-relative-pathname ((component group)) (make-pathname :host (pathname-host (component-pathname (component-parent component))))) (defsystem :foo :components ((:file "packages") (:group "x" :depends-on ("packages") :components ((:file "a") (:file "b" :depends-on ("a")) (:file "c" :depends-on ("b")) (:file "d" :depends-on ("a" "b")))) (:group "y" :depends-on ("packages" "x"") :serial t :components (...)))) Any thoughts? Regards, - Scott Bell

4 4

[asdf-devel] ASDF 1.501
by Faré 02 Feb '10

02 Feb '10

I've just released ASDF 1.501 in the official repository, now with all the source registry configuration that I previously discussed. It's currently documented in its own file README.source-registry, rather than in the general manual asdf.texinfo, as it should be. Patch welcome. Note that I bumped the version from 1.375 to 1.500 then 1.501. This to indicate that we're not using CVS anymore, that I've reached a milestone towards my goal of an "ASDF 2" that I could push as a replacement to ASDF. It passes the tests with SBCL. But the tests could be extended to do more. Next, comes a similar revamp of ASDF-BINARY-LOCATIONS configuration. Or maybe a wholesale replacement of ABL with something that's simpler and configured in a way similar to source-registry? What do YOU think? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] "If men are good, you don't need government; if men are evil or ambivalent, you don't dare have one." — Robert LeFevre

5 17

[asdf-devel] asdf 1.590: now asdf-output-translations
by Faré 02 Feb '10

02 Feb '10

It's raw and unpolished, but on my repo is first attempt at an asdf-output-translations. If anyone cares to get a look and comment, or even test, there's great! http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The problem with being a citizen of the world is that you don't get to travelling abroad much.

1 0

[asdf-devel] Enabling the cache by default
by Faré 02 Feb '10

02 Feb '10

Attila suggested that the ASDF output cache be enabled by default. I think that's a good idea, but didn't dare propose it here because of concerns with backwards compatibility. Does anyone think we should keep the cache disabled by default? Speak now, or remain silent forever! [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] "almost all programming can be viewed as an exercise in caching" — Terje Mathisen, well-known programming optimization guru

1 0

[asdf-devel] asdf output locations
by Faré 02 Feb '10

02 Feb '10

My plan for ASDF 1.600 is to rename the (recently) builtin asdf-binary-locations to asdf-output-locations and make a few incompatible changes to it. * These changes will allow for configuration through an API similar to the one I introduced for the source-registry in 1.500. * I don't think many people use bleeding-edge enough ASDF to have the builtin ABL and these kinds of people would easily adapt anyway * This API will allow the future common-lisp-controller to plug nicely into ASDF through a supported API that doesn't break other stuff and isn't broken by it. * It will also bring all the binary location advantages of asdf-binary-locations, common-lisp-controller or CL-launch to everyone with a single, well-documented, supported configuration mechanism. I committed the following document to explain my current plans, and would appreciate comments: http://common-lisp.net/gitweb?p=projects/xcvb/asdf.git;a=blob;f=README.asdf… [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Wishing without work is like fishing without bait. — Frank Tyger

5 13

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel February 2010