RE: [PEAR-DEV] Fix this FAQ ! (was: [PEAR-BUG] Bug #923)

>Oh yes, and BTW we wouldn't have wasted so much bandwidth and time (3 >releases just to fix wrong install paths...) if you had listened to me in >the first place when I said, "look at other package.xml files", use >role="doc". I guess you didn't even try. If it were documented this wouldn't be a problem. >Being deaf to recommendations from people who have been working on PEAR for >many years to try to make it consistent won't help. Indeed it is a _recommendation_. As I already said, I will not change anything until I see it in the official docs. Perhaps you perceive this as being unreasonable, but I **don't like** the suggestion, I think it confuses things and I don't care how many packages do it that way. I think its utterly stupid to have individual directories for every category and then place the documentation in an outside directory that recreates directories for each package. The examples belong where the package file is. This is confusing, it isn't user-friendly, and I'm not doing it. As far as me _not trying_ I used the FAQ pages to format the package.xml file. Shouldn't all this be explained clearly in those pages? Relying on looking at how other packages do it by downloading those packages and looking at their files leaves room for error and inconsistency. When I did my package.xml file I found sufficient information in the docs to form it. Granted I have had a few errors, but hey, I'm only human. What if the author of that package doesn't have it right in their package? Therefore for the sake of consistency, which I'm sure we all advocate, I have relied on the official documentation. Regards, Richard York