On 2013/08/04 12:27, Antoine Jacoutot wrote: > On Sun, Aug 04, 2013 at 11:05:04AM +0100, Stuart Henderson wrote: > > On 2013/08/04 11:46, Landry Breuil wrote: > > > All this is covered by: > > > > > > Look in /usr/local/share/doc/pkg-readmes for extra documentation. > > > > > > Imagine that we'd display the whole readme or dozens of other messages > > > for all packages you've just installed. Would you scroll back through > > > all of it ? no. > > > > The output for rc.d scripts is quite nice; we list the names of actual > > packages which install a new rc script so the user is able to quickly > > spot things they might need to do after running pkg_add. Perhaps it > > would be useful to do this for new READMEs too.. > > Considering the README names are the FULLPKGNAMEs, I don't think it is > of any use to list them. I think what we do right now (pointing users to > the pkg-readmes directory when a README is installed) is enough.
The problem I'm thinking about is when you install something and a dependency has a file in readmes which you need to read, but you don't know the name of that dependency without careful looking through the output of pkg_add. Or you don't know about the not-totally-obvious option of "ls -rtc /usr/local/share/doc/pkg-readmes", and instead try to manually find it in the directory listing when you have a whole bunch of packages installed..