On Sat, Mar 31, 2012 at 10:47:49PM +0200, Rene Engelhard wrote: > On Sat, Mar 31, 2012 at 08:12:39PM +0000, brian m. carlson wrote: > > Debian Policy specifies that a long description should provide enough > > information for the administrator to determine whether to install the > > package. libcmis talks about the CMIS interface, but fails to explain > > I have yet to see a admin who goes over the whole package list and installs > stuff from there (especially when it comes to libs)
I do go through different categories when I need to find an appropriate package. I also like to see what functionality is being installed on my system as a dependency. In some cases, the dependency is excessive (a full JRE instead of a headless JRE), unneeded (a dependency on gawk that works fine with mawk), or something I just don't want on my system (php). I like to be able to make a quick assessment of what's on my system, and having a complete package description is useful for that. > > what CMIS is or why I might want to interface with it. Perhaps some > > additional text might be useful here. > > http://www.google.com/search?q=CMIS, first link. Yes, I understand that I can use Google to find the information (and I did, in fact, do that before I filed the bug), but I should not have to do that when I'm using aptitude. As an example of something I think would be sufficient, I've provided the following sentence: CMIS stands for Content Management Interoperability Services, a standard for manipulating document management systems. > [ bascially just packaged because LibreOffice started to use it ] I figured that. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
