On Mon, May 09, 2016 at 06:11:08PM +0200, Ingo Schwarze wrote: > So, bzip2(1) is actually an excellent example. > > These lines are required: > > @man man/man1/bzcat.1 > @man man/man1/bzcmp.1 > @man man/man1/bzdiff.1 > @man man/man1/bzegrep.1 > @man man/man1/bzfgrep.1 > @man man/man1/bzgrep.1 > @man man/man1/bzip2recover.1 > @man man/man1/bzless.1 > @man man/man1/bzmore.1 > > These two could be commented out: > > @man man/man1/bzip2.1 > @man man/man1/bunzip2.1 > > You think any porter would get that right? > You feel like coding magic to automate that? > You want to deal with bug reports in case it breaks? > > Part of the reason stuff works so smoothly in the base system is > the high quality of base system manuals. They just don't contain > weirdness of the kind found in bzip2(1).
Just a survery of how many MLINKS we're talking about would be a good idea. Does it make a significant change wrt inode usage and makewhatis runtime ? If base is an outlier (many MLINKS), fine.
