add better report function to duplicate-name condition

[Robert P. Goldman]

TCR reports as follows:

I was just bitten by a duplicate-name condition. It was on ASDF1, but
the code still seems to be exactly the same in ASDF2.

Please add a proper error message to that condition.

I first thought there are two systems with the same name, but it
actually complains about two files with the same name in the same
component.

[Stelian Ionescu (sionescu)]

On Wed, 2010-04-07 at 13:33 +0000, Robert P. Goldman wrote:
> Public bug reported:
>
> TCR reports as follows:
>
> I was just bitten by a duplicate-name condition. It was on ASDF1, but
> the code still seems to be exactly the same in ASDF2.
>
> Please add a proper error message to that condition.
>
> I first thought there are two systems with the same name, but it
> actually complains about two files with the same name in the same
> component.

I encountered this error when testing the patch in bug #556804: when
changing the class of a file from cl-source-file to
cl-restricted-source-file, asdf2 signaled that error in FIND-SYSTEM

--
Stelian Ionescu a.k.a. fe[nl]ix
Quidquid latine dictum sit, altum videtur.
http://common-lisp.net/project/iolib

[Robert P. Goldman (rpgoldman)]

I'm not sure what to make of this comment. Are you saying that this error was incorrectly signaled in response to a different error condition? Or because somehow the change-class caused there to be two components with the same name? If so, is that a different bug?

[Faré (fahree)]

I added a :report function. Are you satisfied?