asdf-devel August 2009

asdf-devel@common-lisp.net

10 participants
22 discussions

[asdf-devel] recursiveness of :FORCE
by Tobias C. Rittweiler 09 Nov '09

09 Nov '09

When I use :FORCE, in most cases I do want to recompile solely the specified system, not all its dependencies. In my ideal world, :FORCE T would recompile the specified system only, and :FORCE :ALL would recompile it along its dependencies. Of course that would be backwards-incompatible, so perhaps better stick with the current behaviour for :FORCE T, but add :FORCE :SYSTEM, or :FORCE :SHALLOW, or similiar. -T.

2 5

[asdf-devel] patch system-source-file
by Greg Pfeil 25 Sep '09

25 Sep '09

Here are a couple changes to ASDF that I made in the process of creating an ASDF browser for CCL's IDE: • system-source-file now works for systems without their own .asd • optional parts of systems (version, maintainer, etc.) don't leave their slots unbound

7 17

[asdf-devel] ASDF features under discussion
by Juan Jose Garcia-Ripoll 23 Sep '09

23 Sep '09

Now that this discussion is opened, I would like to add a small question and a petition. First the question. What is the level of integration of ASDF with different implementations? Does ASDF support all lisp implementations equally? Does SBCL (and perhaps other) ship the latest versions of ASDF? I am asking this because ECL has some pretty special needs. Namely, ASDF currently relies on compile-file / load for everything and for us it is more efficient to compile many files into a single binary that is loaded at a later point. Currently ECL solves this using a slightly outdated version of ASDF, providing its own operations and imposing around methods on different operations. http://ecls.git.sourceforge.net/git/gitweb.cgi?p=ecls/ecl;a=blob;f=contrib/… For instance, we have a LOAD-FASL-OP that joins three steps: 1) a LOAD-OP that thanks to the around methods produces both FASLs and object files, 2) linking the object files into a big FASL, 3) loading the big FASL. If the big FASL has been produced, then only step 3) is performed. But in addition to this ECL provides operations for creating standalone executable files, shared libraries and statically linked libraries http://ecls.sourceforge.net/new-manual/ch16.html I am aware that ASDF is a rapidly evolving architecture and I am afraid that things would break. It is for this reason that I would like to ask for help in one of these ways: 1) providing a stable way for us to implement these extensions or 2) including those operations in ASDF. Juanjo On Wed, Aug 19, 2009 at 3:11 PM, Gary King<gwking(a)metabang.com> wrote: > For the record, we've had recent (but not definitive) discussions of: > > * whether or not optional parts of a system should be `nil` or unbound > > * version numbering > > * integrating ASDF and testing > > * ASDF and the windows symlink patch. > > If there are things I missed in the above list, please let me know. -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com

5 7

[asdf-devel] Recognizing directories in a component name
by Faré 12 Sep '09

12 Sep '09

For years now, we at ITA have been satisfied with a patch that does the following while building QRes: allow to specify module names that include a directory component, without having to redundantly as in (:module "subdir1/subdir2" :components ((:file "subdir3/name3") (:file "subdir4/name4.subname4"))) instead of the cumbersome (to be portable): (:module "subdir1/subdir2" :pathname #.(make-pathname :directory '(:relative "subdir" "subdir2")) :components ((:file "subdir3/name3" :pathname #.(make-pathname :directory '(:relative "subdir3" :name "name3"))) (:file "subdir4/name4.subname4" :pathname #.(make-pathname :directory '(:relative "subdir4" :name "name4.subname4")))))) Since there is active ASDF development again, I cleaned it up and here it is. The methods should replace those currently in ASDF. The helper function now uses the existing ASDF split function (as previously requested by Xof). The patch is both backwards compatible and portable, in that * the "/" character was previously forbidden in names of portable components without a :pathname statement, least it breaks miserably on most platforms. * the "/" character is now recognized by ASDF itself as a separator for directories later made with make-pathname, thus doing what is expected even on the odd platform without "/" as the pathname separator. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Selfishness is the measure of all good (and bad) in the world. There cannot be any good whatsoever without a self to feel it. WHO is whatever "altruistic" oppression ever good for? No one. Why is gratuitous vandalism or well-intentioned mass murder bad? Not because it is selfish, but precisely because it hurts other people's selfish interest.

3 5

[asdf-devel] [OT] Git resources
by Daniel Herring 31 Aug '09

31 Aug '09

Here are a few links that might be helpful to people learning git. Its culturally different than CVS; but once you learn it, there's no turning back. The ability to experiment with local branches, back up, rewrite history, and only publish the sanitized history is quite liberating. http://tomayko.com/writings/the-thing-about-git http://progit.org/book/ http://git-scm.com/documentation http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://www.kernel.org/pub/software/scm/git/docs/everyday.html http://www.kernel.org/pub/software/scm/git/docs/user-manual.html My suggestions - always have `gitk --all` loaded for the repo you're working on - update (not reload) gitk after modifying any branches or tags; this leaves the old objects displayed - `git reset --hard $OLDSHA1` can clean many messes, letting you try again. - reload gitk to hide deleted branches you're comfortable with losing - learn by playing around with local clones of a larger repository - install some of the git contribs, especially git-completion.bash and git-new-workdir Later, Daniel

3 2

[asdf-devel] announce: asdf 1.361
by Gary King 27 Aug '09

27 Aug '09

This release includes the not very well tested window's shortcut handling code that Daniel Herring patched into his version and I merged into the mainline. It also includes several documentation fixes from Robert Goldman and fixes the issue Faré noticed with respect to `nil` values in sysdef-central-registry-search. From the [changelog][]: * Merge with Daniel Herring's Windows link patches * add \*resolve-symlinks\* defvar to determine whether or not ASDF should resolve symlinks when determining a system's pathname * rather than raising an error, silently ignore `nil` values in the sysdef-central-registry-search. * pull system pathname determination logic out of defsystem and into `determine-system-pathname` function * tweak documentation [changelog]: http://common-lisp.net/project/asdf/changelog.html Enjoy, -- 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] Quick asdf.texinfo patch
by Robert Goldman 27 Aug '09

27 Aug '09

I noticed today that the defsystem grammar info node does not include the :class option. The attached patch fixes that. diff --git a/asdf.texinfo b/asdf.texinfo index cfef5c6..b539182 100644 --- a/asdf.texinfo +++ b/asdf.texinfo @@ -339,7 +339,8 @@ option := :components component-list | :operation-done-p method-form | :depends-on ( {dependency-def}* ) | :serial [ t | nil ] - | :in-order-to ( {dependency}+ ) + | :in-order-to ( {dependency}+ ) + | :class symbol component-list := ( {component-def}* )

2 1

[asdf-devel] Loading another system for an operation?
by Robert Goldman 27 Aug '09

27 Aug '09

Here is a case that I haven't encountered before using ASDF, that seems like an interesting one: Imagine that you have a system S, with a new component class, C in it. Further there is an operation O that you MAY need to perform on the components of class C. In order to perform operation O on C, you need to have system S1 loaded. However, if O is unnecessary, then you don't need to load S1. In this case, S does not really depend on S1. You only want to load S1 if there's some component of class C such that the operation-done-p test on O and C fails. Otherwise S1 should not be loaded. So how do we record this dependency? I had thought of attaching it to the actual method of component-depends-on for O and C, but that won't work because when we look up the name of S1, it will be relative to C's parent, so ASDF will be looking for components of S, not for other systems.... I can break that with an around method on FIND-COMPONENT, but thought that might be the wrong thing.... If I was to attach the dependency to performing the operation O onto the system S, then I believe S1 would always be loaded --- unless I record that operation-done-p O S is T if operation-done-p is T for all of the children of class C. That may be the right thing to do, but seems quite cumbersome. This seems like it would be a common use case -- the dependency is really a dependency for the transformation, not for the code that's actually loaded -- so I'm wondering if anyone's encountered it before and handled it more elegantly than I am... Cheers, r

1 0

[asdf-devel] announce: ASDF 1.359
by Gary King 24 Aug '09

24 Aug '09

Patch for system-source-file from Greg Pfeil * system-source-file now works for systems without their own .asd * moved defgenerics to their own section because I like it that way. Documentation improvements * added docstring to the method-combination standard-asdf-method- combination * added docstring to the generic-function traverse * added description of `test-op` to the manual * removed descriptions of test-system-version operation and feature- dependent-op thanks to all, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

4 7

[asdf-devel] contradiction in ASDF central-registry default vs code
by Faré 21 Aug '09

21 Aug '09

The default for ASDF's *central-registry* in SBCL contains a (let (...) (when ...)) which can and *will* return NIL in some cases (i.e. when an executable SBCL image is run). On the other hand, sysdef-central-registry-search calls directory-pathname-p on each entry, which assumes that NIL is an invalid entry. My proposed solution: directory-pathname-p should check that its argument is indeed a pathname designator. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices.

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel August 2009