[Nix-dev] Resolution context of `require' paths

[Nicolas Pierron]

2009/6/30 Eelco Dolstra <e.dolstra at tudelft.nl>:
> Eelco Dolstra wrote:
>
>> Nicolas Pierron wrote:
>>
>>> On Tue, Jun 30, 2009 at 09:50, Ludovic Courtčs<ludo at gnu.org> wrote:
>>>> Hello,
>>>>
>>>> The `modular-nixos' branch introduces `require' statements, which now
>>>> take a path, e.g.,
>>>>
>>>>  require = [ ./nixos/hardware/network/intel-4965agn.nix ];
>>>>
>>>> The problem is that the resolution context of this relative path is
>>>> often problematic.
>>> I don't consider this being a problem.
>>
>> I do consider this a problem:
> [...]
>
> And I forgot:
>
> - The filenames aren't documented anywhere, as opposed to the configuration
> options.  Grepping the source tree for something that looks like the right
> module for your hardware isn't very nice :-)

This part is not necessary if you can generate the configuration.
Unfortunately, you might not understand the meaning of the generated
lines.

-- 
Nicolas Pierron
http://www.linkedin.com/in/nicolasbpierron
Lars Rasmussen (Google IO 2009) - Icland is an icland.