On Fri, 19 Oct 2001, Stefan van der Eijk wrote:

> > #2) You say nothing about the reason.
>
> ./configure was looking for /usr/bin/mcopidl, and couldn't find it.
> [stefan@taz OK]$ urpmf /usr/bin/mcopidl
> arts:/usr/bin/mcopidl
> So I added BuildRequires arts.

So is everybody fed up with this kind of flamewar? It's "BuildRequires"
not "Requires", so one doesn't need a sound card before installing
mandrake_desk. Even one installs arts doesn't mean sound card must be
present.


> > #3) All requirements and the "why" of them should be documented for
> > any serious development project. If you can't document why you
> > included the requirement then it's not likely you know. And if you
> > don't know, then don't put it in there. Adding deps just cause it
> > "makes it work" is not software development, it's playing around.

This is better point though. Stefan, if you have added one more line
"configure requires /usr/bin/mcopidl" in the changelog then this
kind of flamewar may not occur right now.

Of course, it doesn't mean one should document why 1+1=2, but for the
less comprehensible things, it's still worthy to write a note about it.

Abel


Reply via email to