asdf-devel September 2009

asdf-devel@common-lisp.net

18 participants
27 discussions

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

11 Sep '09

Hi Daniel, Faré, My apologies for lack of gitcompetence but I'm confused as to what I've done wrong. I've got > [parsnip:/repository/git/asdf] gwking% git describe --tag > 1.363 > [parsnip:/repository/git/asdf] gwking% git push --tags cl.net > Everything up-to-date but, as you both noted, the master repo on http://common-lisp.net/project/asdf isn't right. Is this the problem? (If so, how do I fix it) > [parsnip:/repository/git/asdf] gwking% git branch -r -v > cl.net/master fff0c81 Tweaked many tests to remove many warnings > cvs/HEAD e7e4681 2009-01-10 gwking(a)metabang.com > cvs/dan 2b0f636 Initial import > cvs/master e7e4681 2009-01-10 gwking(a)metabang.com > save/master 5f64961 minor website tweaks thanks, On Sep 9, 2009, at 9:59 PM, Daniel Herring wrote: > Hi Gary, > > Thanks for pushing all the tags to git. Unfortunately, the "master" > branch is one revision behind tag 1.363. As a result, a simple > clone or update from the repository will miss the resolve-symlinks > patch. > > http://common-lisp.net/gitweb?p=projects/asdf/asdf.git > > Later, > Daniel > > > On Wed, 9 Sep 2009, Gary King wrote: > >> 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 >> >> >> >> >> >> >> _______________________________________________ >> asdf-devel mailing list >> asdf-devel(a)common-lisp.net >> http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel >> -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

3 3

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel September 2009