El 12/09/11 16:29, Sven Vermeulen escribió:
> My main concern here is that there will be a place where the number of
> choices is too big.
When that happens we can always split the document and create new per
choice ones, that's what is done with the handbooks for example, true?
> Also, you'll risk getting a higher frequency on
> bug reports on such paragraphs.
Well I have to disagree with that, less more review documents will have
less bug reports than many less reviewed ones.
>  Think for instance bootloaders, how
> would we deal with guides there?
I think the way we do is ok, I mean having different parts for different
bootloaders.
>  I'm sure we do not want to generate
> separate guides for just all this sort of stuff (and then use
> keywords)...
We don't.
> What about making it generic (edit your clock management configuration
> like, like /etc/conf.d/hwclock on ... )?
Well this particular case offers the deal that the configuration to
change is the same (just in different places), the problem with generic
definitions is that they tend to confuse users, and if we specify a
single alternative then users of the others will get even more confused.