>From: Stefan van der Eijk <[EMAIL PROTECTED]> >>#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.
This is what I am talking about - adding a requirement just to make it work. Do you know that mcopidl is REALLY needed, or are you just trying to make ./configure happy? If mcopidl is really needed, then it's obviously NOT just an arts thing and should be taken out and put in a more reasonable place. (I know that isn't what you are working on at the moment - but someone should be). > >>#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. > >The thing is, you can document all of this stuff, produce tonnes of >comments. Will it serve a purpose? If you feel documenting everything in >great detail serves a pupose, please specify with how much detail I >should document the changes I make to the packages. > Any time you add a dependency you should say why. And "to make it work" is not a good reason. :) There are a great many books available on software development - I can guarantee that every one that mentions the subject advises in favor of documentation. It may be a pain in the butt at times, but it can save a lot of bewilderment in the future. _______________________________________ Grimau Lysik'an, The Bionic Elf _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
