Is this RDMD bug ?

[via Digitalmars-d-learn]

On Saturday, 23 August 2014 at 18:43:35 UTC, Vladimir Panteleev 
wrote:
> On Saturday, 23 August 2014 at 18:41:58 UTC, Marc Schütz wrote:
>> On Saturday, 23 August 2014 at 17:41:38 UTC, Dicebot wrote:
>>> On Saturday, 23 August 2014 at 17:37:39 UTC, sigod wrote:
>>>> On Saturday, 23 August 2014 at 17:32:15 UTC, Vladimir 
>>>> Panteleev wrote:
>>>>> No, it is not an rdmd bug.
>>>>>
>>>>> "etc" is a standard D package name reserved for Phobos, the 
>>>>> standard library. It is the same for "std" and "core".
>>>>
>>>> Please, point us directly to a documentation where it says 
>>>> that this words reserved.
>>>
>>> http://dlang.org/phobos/ ?
>>> (you don't expect to casually use package names "std" and 
>>> "core" either, do you?)
>>
>> Why not? If I want to amend the standard library, e.g. for 
>> testing a module that's not yet present in my compiler 
>> version, or for fixing an error? I think it's useful to be 
>> able to override individual modules by placing a copy of them 
>> into your project's directory.
>
> For the record, rdmd handles this particular case just fine. 
> You can run unit tests on any one Phobos module with "rdmd 
> -main -unittest module.d". The package exclusion list only 
> applies to imported modules.

But imported modules are the important case. If I have an 
important bugfix in a module, and don't want to wait for the next 
release, what am I supposed to do?

I don't know how rdmd works exactly, but AFAICS `dmd -deps` 
already outputs the full paths of the imported files, 
recursively. Isn't that enough?