asdf-devel

asdf-devel@common-lisp.net

5 participants
1375 discussions

Start a nNew thread

[asdf-devel] [Fwd: Re: I think new ASDF has busted asdf-binary-locations]
by Robert Goldman 09 Sep '09

09 Sep '09

Whoops. Forgot to reply-all (different mailing lists have different policies...). R

1 0

Re: [asdf-devel] I think new ASDF has busted asdf-binary-locations
by Gary King 09 Sep '09

09 Sep '09

(cc'd to list) Damn. The function disappeared recently (by my hand). I didn't realize (obviously) that it was used. I'll fix. On Sep 8, 2009, at 11:17 PM, Robert Goldman wrote: > I just updated, and now can't start up lisp because > asdf-binary-locations calls ASDF::RESOLVE-SYMLINKS which seems to have > vanished from asdf.lisp. > > Any insight? > > r -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

5 9

[asdf-devel] announce - asdf 1.363
by Gary King 09 Sep '09

09 Sep '09

This release restores the `resolve-symlinks` function which I had removed while cleaning up without realizing that ASDF-Binary-Locations made use of it. Thanks to Robert Goldman for the catch. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

2 1

[asdf-devel] *ASDF-REVISION*
by Robert Goldman 08 Sep '09

08 Sep '09

Should I expect the *ASDF-REVISION* variable to work for me? Right now it's NIL. Is the definition of *ASDF-REVISION* a holdover from the CVS days, and no longer working, or is this YA case where there's something about git that I'm missing? Should I be doing something with the git pull that will get me a tags directory? thanks, r

3 7

[asdf-devel] announce - ASDF 1.362
by Gary King 08 Sep '09

08 Sep '09

This release mostly fixes my confusion... I was mistakenly developing on a branch instead of on master and this meant that my recent patches didn't make it out to the world in the manner intended. Thus, this release actually contains the Windows shortcut code, etc. enjoy, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

2 2

[asdf-devel] Slight unportability in %DEFINE-COMPONENT-INLINE-METHODS
by Tobias C. Rittweiler 06 Sep '09

06 Sep '09

%DEFINE-COMPONENT-INLINE-METHODS contains the following LOOP form: (loop for data = rest then (cddr data) while data for key = (first data) for value = (second data) ...) However, if you look at LOOP's BNF in the specification, you'll see that termination clauses *must* appear after :for clauses. CLISP rightfully signals a warning. -T.

5 4

[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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel