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

[asdf-devel] tab-blocking commit hook
by dherring＠tentpost.com 15 Jan '10

15 Jan '10

The attached script should prevent tabs in *.asd, *.lisp, or *.script files from being committed to a git repository. Existing tabs will not be affected, unless they appear in (the context of) another modification. Here's an example stopped commit. "" Error: This git repository disallows the #\Tab character in lisp files. Only spaces should be used for indenting lisp code. In emacs, 'M-x untabify' and (setq indent-tabs-mode nil) may help. First offending file and lines: test.asd + this is a tab "" To install, simply copy this script to .git/hooks/pre-commit and set the executable bit. It might also be good to put a copy somewhere permanent so others can install it to their local repositories. Later, Daniel

4 5

Re: [asdf-devel] 1.374
by Samium Gromoff 22 Dec '09

22 Dec '09

Fare, Please consider the patch in the 'missing-definition' branch in git://git.feelingofgreen.ru/asdf regards, Samium Gromoff -- _deepfire-at-feelingofgreen.ru O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

3 5

[asdf-devel] website
by Tobias C. Rittweiler 21 Dec '09

21 Dec '09

Hi Gary, What are the required steps to change the Website? -T.

1 0

[asdf-devel] 1.374
by Faré 21 Dec '09

21 Dec '09

I released ASDF 1.374 on the official git repository. I don't intend to work on any of the very legitimate bugs that have been reported recently (notably by tcr), but I hope someone else will. Instead, I'll be working on the configurability and upgradability of ASDF, so that we may push a valid, self-upgradable ASDF "once and for all". [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The main reason Santa is so jolly is because he knows where all the bad girls live. 2009/12/19 Nikodemus Siivola <nikodemus(a)random-state.net>: > 2009/12/19 Faré <fahree(a)gmail.com>: > >> If no one objects to any of the contents, I will push to the official >> repo some time next week. > > Ack to all of these: > > commit 4ab91931445316319b621d3b5f8759bf893943ab > Author: Francois-Rene Rideau <fare(a)tunes.org> > Date: Fri Dec 18 19:15:01 2009 -0500 > > From Robert Goldman, docstring for *defined-systems* > > commit 7f4d19be0b870e41d6ab4beb12c94dc3f09a4aa8 > Author: Francois-Rene Rideau <fare(a)tunes.org> > Date: Fri Dec 18 09:18:15 2009 -0500 > > Release 1.373. Remove tabs in all lisp files. > > commit faa8b05b23fa6cca8ca655fb8bb4f77471921540 > Author: Francois-Rene Rideau <fare(a)tunes.org> > Date: Fri Dec 18 09:07:34 2009 -0500 > > untabify asdf. > > commit 3277d20895d6a59c25890725e6df0d3d4ca0958e > Author: Francois-Rene Rideau <fare(a)tunes.org> > Date: Fri Dec 18 09:06:46 2009 -0500 > > Ignore tmp/ directory created by Makefile >

1 0

[asdf-devel] [Patch] Properly set asdf:*asdf-revision* on self-upgrade.
by Tobias C. Rittweiler 20 Dec '09

20 Dec '09

At the moment *ASDF-REVISION* is a DEFVAR which won't be reset on reloading. The attached patch makes it a DEFPARAMETER, so *ASDF-REVISION* will reflect the correct version after a self-upgrade. -T.

2 1

[asdf-devel] last patch
by Robert Goldman 19 Dec '09

19 Dec '09

In trying to dig at one of TCR's bugs, I was archaeologizing asdf.lisp, to figure out the contents of the *defined-systems* table. Put what I came up with into a docstring. cheers, r

3 2

[asdf-devel] [PATCH] *defined-systems* docstring
by rpgoldman＠sift.info 18 Dec '09

18 Dec '09

From: Robert P. Goldman <rpgoldman(a)real-time.com> --- asdf.lisp | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/asdf.lisp b/asdf.lisp index 6cca99b..4660260 100644 --- a/asdf.lisp +++ b/asdf.lisp @@ -588,7 +588,12 @@ and NIL NAME and TYPE components" (defun make-defined-systems-table () (make-hash-table :test 'equal)) -(defvar *defined-systems* (make-defined-systems-table)) +(defvar *defined-systems* (make-defined-systems-table) + "This is a hash table whose keys are strings, being the +names of the systems, and whose values are pairs, the first +element of which is a universal-time indicating when the +system definition was last updated, and the second element +of which is a system object.") (defun coerce-name (name) (typecase name -- 1.6.5.3

1 0

[asdf-devel] More committers?
by Faré 18 Dec '09

18 Dec '09

Tobias, do you want to have the commit bit, so you may check in fixes to the bugs you reported? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Government is a disease masquerading as its own cure. — Robert LeFevre (1911 - 1986)

2 1

[asdf-devel] asdf source registry
by Faré 18 Dec '09

18 Dec '09

2009/12/18 Nikodemus Siivola <nikodemus(a)random-state.net>: > Some questions and notes: > > How do I instrospect *SOURCE-REGISTRY*? The outlined API only puts > stuff there, but doesn't tell me how to read it. > For the moment, I don't have a good story for a public API on how to do that. But considering that only ASDF and XCVB currently will use that registry, and that I can commit in both, I don't think this is a big issue for now: whatever good API I find should do, and won't be exported until it's good and/or someone asks. > I would like to be able to mutate *SOURCE-REGISTRY* (even if by > cloning without actual destructive operations) at runtime to isolate > things. What about a (defmacro with-source-registry ((registry) &body body) ...) ? > Under which circumstances one is expected to use which of the > configuration methods: are libraries that are composed of multiple > systems allowed/expected to ship with configuration files? In > particular, the purpose of the environment variable seems unclear to > me. > Configuration files would probably not be shipped with libraries or programs but possibly generated by scripts that build and/or install the libraries or programs. Indeed, these configuration files contain paths that change from machine to machine (relative paths don't make sense). > Being able to specify individual files seems important to me. Do you have a use case? It would mean that the source registry would contain things that are very specific to the build system being used. Then again, so will it be if you use the "symlink a bunch of .asd files" pattern. > COMMON-LISP-CONFIGURATION: Who will maintain this? What other things > belong in there? I'd say community consensus, starting on the ASDF mailing-list. Other things that belong there would be anything that portably configures the general installation of Lisp software. > Having -SOURCE-REGISTRY-CONFIGURATION as a suffix in all the names > seems excessive. Maybe just -SOURCE-REGISTRY? Possibly. > I'm not sure I see the point of having both INITIALIZE- and ENSURE-, > especially given CLEAR-. Initialize is expensive. Ensure is cheap in amortized costs. For backwards compatibility, ASDF will call ensure a lot. > PROCESS-SOURCE-REGISTRY-CONFIGURATION seems like a bad name, since it > doesn't do that. PROCESS-FOR-SOURCE-REGISTRY maybe? > INITIALIZE-SOURCE-REGISTRY-FROM ? > Caching: you mean caching by ASDF, not by the config system? Yes. > I think I might have a better overall idea of what you intend if you > described this configuration system separately from the ways ASDF > would use it -- in particular since it seems to me several things > might want to use this to manage their own external resources. > Well, apart from the package, I don't see exactly how other programs would use it. Maybe the package should be COMMON-LISP-SOURCE-REGISTRY instead. --#f If you could ask a unique question to a computer during a Turing test, what would you ask? — Douglas Hofstadter, Metamagical Themas

1 0

[asdf-devel] How about a tabs versus spaces policy for asdf?
by Robert Goldman 18 Dec '09

18 Dec '09

I would just be tickled to death if we were to ban tab characters from asdf code (I'm convinced by jwz's argument, and I've been harmed enough times by Windows-versus-others tab issues), but I'd be ok with keeping them. Do we have a consensus on tabs-versus-spaces? Cheerio, r

3 4