asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

[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

Re: [asdf-devel] Pre ML post review
by Faré 18 Dec '09

18 Dec '09

Dear ASDF developers, Rommel and I are currently working on asdf bug #485918, i.e. a plan for user-customizable persistent configuration of ASDF paths through configuration files (duh). https://bugs.launchpad.net/asdf/+bug/485918. What follows is a detailed plan and several questions. General Idea ============ The general idea is that in configuration files such as /etc/common-lisp/source-registry.conf ~/.config/common-lisp/source-registry.conf will be a SEXP in a trival domain-specific language to specify a search path. Backwards Compatibility ======================= Now comes the issue of backwards compatibility with the current asdf:*central-registry* that currently has to be manually configured by users or supplemental layer (e.g. common-lisp-controller). My proposal is that there would be a new (private) variable common-lisp-configuration::*source-registry* that would store a parsed version of the configuration as an undocumented opaque data-structure (except for the private use of ASDF and XCVB), only accessible through API functions and said DSL. One magic directive in that DSL, present by default in the configuration, :default-registry would hook into the implementation defaults, which would include the searching of asdf:*central-registry* until it is eventually removed. Uses of asdf:*central-registry* would be deprecated, but still supported for many years to come for backwards compatibility. The same DSL could be recognized by ASDF, XCVB, and any other future build system for Common Lisp. Alternatives I considered and rejected included: 1- Keep asdf:*central-registry* as the master with its current semantics, and somehow the configuration parser expands the new configuration language into a expanded series of directories of subdirectories to lookup, pre-recursing through specified hierarchies. This is kludgy, and leaves little space of future cleanups and extensions. 2- Keep asdf:*central-registry* remains the master but extend its semantics in completely new ways, so that new kinds of entries may be implemented as a recursive search, etc. This seems somewhat backwards. 3- Completely remove asdf:*central-registry* and break backwards compatibility. Hopefully this will happen in a few years after everyone migrate to a better ASDF and/or to XCVB, but it would be very bad to do it now. 4- Replace asdf:*central-registry* by a symbol-macro with appropriate magic when you dereference it or setf it. Only the new variable with new semantics is handled by the new search procedure. Configuration DSL ================= Here is the grammar of the SEXP DSL I am considering for configuration: ;; A configuration is single SEXP starting with keyword :source-registry ;; followed by a list of directives. CONFIGURATION := (:source-registry DIRECTIVE ...) ;; A directive is one of the following: DIRECTIVE := ;; add a single directory to be scanned (no recursion) (:directory DIRECTORY-PATHNAME-DESIGNATOR) | ;; add a directory hierarchy, recursing but excluding specified patterns (:tree DIRECTORY-PATHNAME-DESIGNATOR &key exclude) | ;; override the default defaults for exclusion patterns (:exclude-subdirectories PATTERN ...) | ;; splice the parsed contents of another config file (:include-configuration REGULAR-FILE-PATHNAME-DESIGNATOR) | ;; Your configuration expression MUST have contain exactly one of these: (:inherit-configuration) | ; splices contents of inherited configuration (:ignore-inherited-configuration) ; drop contents of inherited configuration ;; This directive specifies that some default must be spliced. (:default-registry) PATTERN := a string without wildcards, that will be matched exactly against the name of a subdirectory. Configuration Files =================== Following a suggestion by Stelian, the configuration should be read in this order, each configuration containing an expression that may extend or override the previous configuration: file /etc/common-lisp/source-registry.conf file ~/.config/common-lisp/source-registry.conf environment variable CL_SOURCE_REGISTRY some implementation- or application- specific command-line argument. Equivalently (since the DSL doesn't allow for uncontrolled side-effects), the outermost configuration only would be parsed, and recursing to previous configurations would only happen if and when specified. This also leaves the question of whether environment variable and command-line arguments should take the same SEXP syntax (to be READ), or whether they should have some more shell-friendly textual representation of the same information. Allowing for a different representation is probably more work for marginally more feature, and I don't recommend it. So, in the end, the same SEXP syntax for shell variables and command-line arguments. Configuration API ================= This API is exported from package COMMON-LISP-CONFIGURATION. (initialize-source-registry-configuration) will read the configuration and initialize all internal variables, and return the new configuration. (clear-source-registry-configuration) undoes any initialization. You might want to call that before you dump an image that would be resumed with a different configuration, and return an empty configuration. Also will have a hook that allows clients will use to clear any cache that depends on this configuration. (ensure-source-registry-configuration) checks an initial variable to see whether the state is initialized or cleared. In the former case, return current configuration; in the latter, initialize. ASDF will call this function at the start of (asdf:find-system). (process-source-registry-configuration X &optional inherit) If X is a CONS, parse it as a SEXP in the configuration DSL, and extend or override inheritted configuration. If X is a STRING, first parse it into a SEXP with READ (Alternate proposal: parse some shell-friendly text representation). The inheritted configuration is provided in optional argument inherit, itself a function that returns the previous configuration, with NIL designating the default of #'ensure-source-registry-configuration. Internally, initialize-source-registry-configuration can use this with a series of functions for inheritted configuration. Search Algorithm ================ * When a system is searched for, entries are processed in order. * If a given entry has exactly one match, the search stops successfully. If a given entry contains no match, it is skipped. If a given entry contains multiple matches, an error is thrown. * This later case does not change the semantics of ASDF in the case where no recursion takes place, and ensures no undetected insanity happens in the case where recursion is specified. XCVB has tested this model, with success I believe. * When an entry is first processed, the implementation may cache the contents of the directory (i.e. all files that may match anything.) until the cache is explicitly flushed (see below). Cache flushing ============== * The cache is flushed when function (asdf:clear-system-search-cache) is called. * When the configuration is (re)loaded, the cache is flushed. Questioned Niceties =================== I've been suggested the below features, but have rejected them, for the sake of keeping ASDF no more complex than strictly necessary. * More syntactic sugar: synonyms for the configuration directives, such as (:add-directory X) for (:directory X), or (:add-directory-hierarchy X) or (:add-directory X :recurse t) for (:tree X). * The possibility to register individual files instead of directories. * Integrate Xach Beane's tilde expander into the parser, or something similar that is shell-friendly or shell-compatible. I'd rather keep ASDF minimal. But maybe this precisely keeps it minimal by removing the need for evaluated entries that ASDF has? i.e. uses of USER-HOMEDIR-PATHNAME and $SBCL_HOME Hopefully, these are already superseded by the :default-registry * We may allow a shell-friendly colon-separated text-based syntax for environment variables and command-line arguments. If we only accept directories, not files, then all provided strings should be considered with implicit / at the end before being parsed by parse-namestring or such. An explicit // (as in TEXINPUTS) or /** (as in zsh or some (non-standard) CL pathname extensions, but requiring painful quotes from the shell) could specify recursion. Additional Notes ================ With this specification, we can share configuration between ASDF and XCVB, and maintain reasonable backwards compatibility in ASDF. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Just because your semi-free country government is evil doesn't mean "native" governments have a right to exist and enslave "their" people. — Faré

3 2

[asdf-devel] testing latest release with allegro
by Robert Goldman 09 Dec '09

09 Dec '09

With Allegro 8.1 in both ANSI and modern (case-sensitive) modes, two of the tests fail: test-retry-loading-component-1.script test-utilities.script I have not yet had a chance to debug this. This message may bounce from asdf-devel, since I have had to send it from gmail (linux box doesn't have configured email). I have not yet tested with CCL or ABCL, the other two CL implementations available to me. Tests pass on SBCL, which I presume you have already checked. Best, r

1 0

[asdf-devel] What is the release process for ASDF?
by Faré 09 Dec '09

09 Dec '09

Beside running tests with SBCL, what is the release process for ASDF? Are there a script to automatically increase the revision number, commit, build tarballs, update online documentation? The bin/ directory suggests there are, but it's unclear what is the correct usage pattern (if any), and I'd rather not learn the gotchas the hard way. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] The worst thing about totalitarian regimes is not that they make people poor, miserable and unfree -- it's that they corrupt people's souls, and turning everyone into a double-thinking, double-speaking liar for the sake of survival.

5 9

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel