I will quote once more from the Policy. 3.4, The description of a package: > The description should describe the package (the program) to a user > (system administrator) who has never met it before so that they have > enough information to decide whether they want to install it.
In other words, it’s the phrase with which a package introduces itself: “Hi! I’m [firefox], a [Safe and easy web browser from Mozilla].” “Hello! My name is [bzr], I am an [easy to use distributed version control system]”. Note how the description extends on the package name and does not (and need not) make sense without it. When I installed Ubuntu for the first time, I knew no preinstalled packages by name and it might be convenient if they introduced themselves at first, second, maybe fifth update. Now that I’ve been using Ubuntu for 6 years straight, it’s getting silly. If you want to argue that bzr should be named bazaar, no problem. File a bug against bzr, so that it be renamed and bzr made a transitional dummy package. But please do not ask that bzr be *described* as “Bazaar”: this description says nothing to help me decide if I want it. The solution is not to put program titles into the description, it is to show package names *along with* the description. BTW lintian complains not only at package name included literally in the synopsis line, but also with minor changes, e.g. in letter case. So e.g. putting the word “Firefox” in the synopsis won’t fly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180899 Title: Update list hides important details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1180899/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
