Suggestions for procedure going forward

We have had a number of ASDF 3 releases that have mostly been aimed at bug-fixing (although some new features have crept in). I'd like to declare ASDF 3 feature complete and done, but I don't want to close the door to future bug fix releases as needed, nor do I want to shove incomplete new

make-pathname* and Allegro

We were debugging some problems with an internal system and happened to run across this: (defun make-pathname* ( keys (directory nil) host (device () #+allegro devicep) name type version defaults #+scl ) "Takes

Re: make-pathname* and Allegro

On Tue, Nov 17, 2015 at 1:11 PM, Kevin Layer wrote: > We were debugging some problems with an internal system and happened > to run across this: > > (defun make-pathname* ( keys (directory nil) > host (device () #+allegro devicep) name >

Re: make-pathname* and Allegro

Faré wrote: >> Dear Kevin, >> >> That change was just a reindentation. If you keep going along the git >> blame ${VER}^ -- pathname.lisp history, you find that the commit that >> introduced this line is 96cecd29 (2.26.85, citing "More pathname >> madness for allegro"), but it only generalizes

Re: make-pathname* and Allegro

Faré wrote: >> I ran the tests after gutting make-pathname* from any non-trivial >> wrapping around make-pathname, and make t l=allegro still passes. >> >> I gutted this function, with a complete explanation in the commit >> message. Thanks! Very cool! Thanks.

Re: Suggestions for procedure going forward

On 11/17/15 Nov 17 -4:00 PM, Stelian Ionescu wrote: > On Tue, 2015-11-17 at 11:11 -0600, Robert Goldman wrote: >> We have had a number of ASDF 3 releases that have mostly been aimed at >> bug-fixing (although some new features have crept in). >> >> I'd like to declare ASDF 3 feature complete and

Re: Finding depended-upon systems

> Once in a long while I've wanted to get a list of all of the source > files, or the fasl files, a dependency graph (tree?). Mostly just to > see what the system thinks it has and what I think it should have. > There is a contrib/ directory in asdf repository, but its downside is that having the

Re: Suggestions for procedure going forward

On Tue, Nov 17, 2015 at 6:07 PM, Robert Goldman wrote: > On 11/17/15 Nov 17 -4:00 PM, Stelian Ionescu wrote: >> On Tue, 2015-11-17 at 11:11 -0600, Robert Goldman wrote: >>> We have had a number of ASDF 3 releases that have mostly been aimed at >>> bug-fixing (although some new

Re: Suggestions for procedure going forward

On 2015-11-17 18:11 CET, Robert Goldman wrote: > [...] > So I'd like to split ASDF development into stable and testing or > something like that. > > Does anyone have experience doing that? If so, please post suggestions > for process to ASDF-devel. If we have to support

Finding depended-upon systems

This seems like it might be a good FAQ, and we had some correspondence about a related query earlier. (sort (mapcar #'asdf:component-name (mapcar #'cdr (remove-if-not #'(lambda (x) (and (typep (cdr x) 'asdf/system:system) (typep (car x)

Re: make-pathname* and Allegro

On Tue, Nov 17, 2015 at 1:51 PM, Kevin Layer wrote: > Faré wrote: > >>> Dear Kevin, >>> >>> That change was just a reindentation. If you keep going along the git >>> blame ${VER}^ -- pathname.lisp history, you find that the commit that >>> introduced this line is 96cecd29

Re: Finding depended-upon systems

> "Robert" == Robert Goldman writes: Robert> This seems like it might be a good FAQ, and we had some correspondence Robert> about a related query earlier. [snip] Robert> Maybe we should wrap this up and provide it as part of an ASDF query API? These kinds

Re: Finding depended-upon systems

On Tue, Nov 17, 2015 at 3:37 PM, Robert Goldman wrote: > This seems like it might be a good FAQ, and we had some correspondence > about a related query earlier. > > (sort (mapcar #'asdf:component-name >(mapcar #'cdr >

Re: Finding depended-upon systems

On 11/17/15 Nov 17 -3:10 PM, Faré wrote: > On Tue, Nov 17, 2015 at 3:37 PM, Robert Goldman wrote: >> This seems like it might be a good FAQ, and we had some correspondence >> about a related query earlier. >> >> (sort (mapcar #'asdf:component-name >>

Re: Finding depended-upon systems

Robert Goldman wrote: >> There was some discussion about this in connection with finding what >> needed to be recompiled. Is the latter even a query that ASDF can >> answer? In old ASDF we computed the plan first, and only after that did >> we decide whether the operations

Re: Finding depended-upon systems

Also, note that this fails to find defsystem-depends-on systems, and, what is worse, that ASDF will fail to reload them then reload the .asd files that depend on it when these systems change. See https://bugs.launchpad.net/asdf/+bug/1500578 —♯ƒ • François-René ÐVB Rideau •Reflection•

Re: Suggestions for procedure going forward

On Tue, 2015-11-17 at 11:11 -0600, Robert Goldman wrote: > We have had a number of ASDF 3 releases that have mostly been aimed at > bug-fixing (although some new features have crept in). > > I'd like to declare ASDF 3 feature complete and done, but I don't want > to close the door to future bug