Bug#442117: the package descriptions are still not really descriptive
reopen 442117 thanks * Debian Bug Tracking System [EMAIL PROTECTED] [2007-09-19 17:39:16 CEST]: Their explanation is attached below. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact John Goerzen [EMAIL PROTECTED] by replying to this email. It would be nice if you could elaborate how you call that a fix. Yes, the mentioned empty paragraph doesn't exist anymore - but the new description isn't helpful neither. The long description is expected to contain of at least full sentences, which it doesn't. It says it lets one keep an eye on the status, where it doesn't explain in what way, and what kind of tray is meant, like I asked in my original message... Furthermore you doesn't seem to have touched the bacula-client description at all. Please notice that the package description is the thing that should give the user all needed informations about wether he wants to install the package at all, and this isn't giving out any. Please read up about helpful hints on how to write proper package descriptions in the developer's reference[1]. Thanks for taking care of this helpful piece of software, btw. Rhonda [1] http://www.at.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-desc-basics -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442117: the package descriptions are still not really descriptive
On Thu September 20 2007 1:46:22 am Gerfried Fuchs wrote: It would be nice if you could elaborate how you call that a fix. Yes, the mentioned empty paragraph doesn't exist anymore - but the new description isn't helpful neither. The long description is expected to contain of at least full sentences, which it doesn't. It says it lets one keep an eye on the status, where it doesn't explain in what way, and what kind of tray is meant, like I asked in my original message... If you don't like it, why not suggest your own? I don't use traymonitor myself, and my Bacula environment does not include X capabilities anyhow. Furthermore you doesn't seem to have touched the bacula-client description at all. Please notice that the package description is the thing that should give the user all needed informations about wether he wants to install the package at all, and this isn't giving out any. The bug was submitted against bacula-traymonitor. Looking back at the report, I see I missed the sentence about bacula-client. It would have been better to submit two bugs, or one bug against the bacula source package, here. But, in general, I see no need to duplicate a paragraph of text from the bacula package in every single other package. See, for instance, claws-mail-plugins, education-laptop. -- John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#442117: the package descriptions are still not really descriptive
* John Goerzen [EMAIL PROTECTED] [2007-09-20 15:28:39 CEST]: On Thu September 20 2007 1:46:22 am Gerfried Fuchs wrote: It would be nice if you could elaborate how you call that a fix. Yes, the mentioned empty paragraph doesn't exist anymore - but the new description isn't helpful neither. The long description is expected to contain of at least full sentences, which it doesn't. It says it lets one keep an eye on the status, where it doesn't explain in what way, and what kind of tray is meant, like I asked in my original message... If you don't like it, why not suggest your own? Because I am still not sure about what it is for and why I should install it, because it doesn't mention anything useful. But for a start, writing full sentences shouldn't be that much of a problem, not? But, in general, I see no need to duplicate a paragraph of text from the bacula package in every single other package. See, for instance, claws-mail-plugins, education-laptop. I took a look at them both, and they both are better examples than the bacula-client long description, yes. Besides, naming other bad examples doesn't make your description any better, it just shows that the overall quality and usefulness of package descriptions isn't high. So long, Rhonda -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
