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

[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

[asdf-devel] Question about git
by Robert Goldman 31 Jan '10

31 Jan '10

How are we supposed to be reasoning about the multiple git repositories out there? I have been pulling from the master/public one and then working locally. Fare works on his personal working copy. When I make a patch on mine, based on public, seems like I sometimes end up with patches that Fare can't apply cleanly to his. How are we supposed to handle this? Thanks, r

5 12

Re: [asdf-devel] asdf v 1.501: doesn't look at /etc/common-lisp/source-registry.conf.d/
by Faré 30 Jan '10

30 Jan '10

Oops, you're right. So here's ASDF 1.502. Also includes a fix to bug 513338 (ccl support in test). [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Living your life is a task so difficult, it has never been attempted before. On 30 January 2010 16:14, Peter Van Eynde <pvaneynd(a)debian.org> wrote: > Looking into the code I vaguely think that we are missing a call to > > (process-source-registry (system-source-registry-directory-pathname) > > somewhere, not?

1 0

Re: [asdf-devel] Bug#560781: (require :package) no longer works for CLC-managed packages
by Faré 29 Jan '10

29 Jan '10

2010/1/20 Peter Van Eynde <pvaneynd(a)mailworks.org>: > instead of /etc/common-lisp/source-registry.conf I would like to see > /etc/common-lisp/source-registry.conf.d > > where instead of having one file that you might have to edit in > post-installation scripts we would have a directory where packages can > just drop files into. Just like we have /etc/crontab and /etc/cron.d/* > on Debian. > > This would make my and I suspect others work much easier. > Makes perfect sense. I'll add that on top of my TODO list for ASDF. Would that replace source-registry.conf altogether, or override it, or be overridden by it? >> Since ASDF-BINARY-LOCATIONS is now part of ASDF, I suppose it could be >> similarly configured, and CLC could and should "just" use that. What >> do you think? > > I just noticed this in the manual and need to read it with more > attention later. Ideally I would like it to handle also 'cached' fasl > files from a trusted system user. Would it be able to do this too? > I probably would do it, if we coax it to our will. Definitely possible. I admit I never looked into ABL myself, having only ever used but my own variant (included in cl-launch) that itself is derived from an earlier CLC and works well with CLC. Hopefully, moving ABL into ASDF was a good move, and we should get the configuration of it right. > So load from > /var/cache/common-lisp-controller/cl-builder/<implementation>/... > or > /var/cache/common-lisp-controller/<userid>/<implementation>/... > or compile from /usr/share/common-lisp-controller/source/... to > /var/cache/common-lisp-controller/<userid>/<implementation>/... > Yes. All the while, the default might be something like ~/.cache/common-lisp/<same-tag-as-slime>/... > Related: I might go for a business trip to Boston in the near future and > would love to have a chat! I would love to see you again! [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] He who refuses to do arithmetic is doomed to talk nonsense. — John McCarthy, in his webpage on Progress and Sustainability

2 2

[asdf-devel] subtle bugfix [for clisp on windows]
by dherring＠tentpost.com 28 Jan '10

28 Jan '10

Thank you git-bisect. The attached patch fixes my problems with asdf and clisp on mswinxp32. It fixes what I believe was a typo in commit 2ca055895. Surprisingly, it works on most implementations. - Daniel

2 1