asdf cvs interplay with pathnames

[Levent Guel]

Hi all asdf users,

I just found out that having a CVS root folder for cvs related checkouts of sbcl is a bad thing:
for example

my sbcl cvs checkout resides in /mnt/sources/sources/CVS/sbcl

i have a GIT repo under /mnt/sources/sources/GIT/sbcl too

the problem with building was that the cvs version would not build contrib's which use asdf. In the above cvs version the only built contrib modules were asdf, sb-executable and sb-sprof, whereas the GIT version would build all the contrib modules successfully.

After having a discussion about what the problem maybe, someone on #sbcl channel told me that it maybe due to the interplay of asdf and cvs and my naming scheme there, but suggesting me to put that as an actual bug here. We got all through checking (logical-pathname-translations "SYS") in both cases without success, the pathnames were the same in both cases. so what remains is a warning to be directed at asdf users, who use pathnames like that above, and/or a warning at the asdf maintainers to check into account, that asdf may pose problems with cvs and cvs-matadata handling in certain cases.

[3b (00003b)]

To clarify (as the 'someone on #sbcl'), the problem is that while the manual says "Exclude statements specify patterns of subdirectories the systems from which to ignore." it seems to be matching parent directories too, as in the example above while searching for SBCL contribs, which matches the default exclude of "CVS" subdirectories.

After looking further though, it may have been fixed in 2.139/2.010 while optimising directory search.

[Levent Guel (levent-guel)]

yep the newest checkout of asdf 2.010.3 TAG 2.147 seems to solve the problem

[Faré (fahree)]

Easiest bug fix ever!