On Mon, Jan 29, 2007 at 10:32:30AM +0100, Robert Millan [ackstorm] wrote:
> On Sat, Jan 27, 2007 at 04:54:48AM +1030, Ron wrote:
> > The Suggests seems like a friendly compromise between "every binary
> > should have a man page" and the fact that the man pages have been
> > declared non-free.
> > 
> > I could remove the links entirely and simply accept the former bug
> > until we have free docs again, but I really don't think this is worth
> > an entirely new non-free source package, just for a couple of symlinks.
> 
> Why don't you check in postinst wether the actual manpages exist, and
> set the symlinks only if they do?

We'd have to pre-depend on a non-free package for that to be reliable
though.  A well defined, easy to remedy bug that skirts around policy
seems preferable to an intermittent one that requires a forced reinstall
or The Big Hammer to fix.

> cpp-doc postrm could check wether someone is linking to its manpages,
> and remove the links if applicable.

If this were a general issue, that might be an option to explore, but
afaik its only this package affected, so I'm not terribly keen on the
idea of infecting another package with a workaround also...

Maybe I'm wrong but I'd guess a large proportion of people using this
would also tend to have the toolchain docs installed.  For those that
don't want them, they are pretty certain to have the rm tool handy ;-)

That's not the sort of answer I'm typically fond of, but it works for
those who thought they already had the docs and install them when the
dangling links point that out, as well as being a well known generic
solution for dangling symlinks left by whatever means as happens from
time to time...

In the absence of a real solution, that seems pretty close to line of
least surprise.  I'll leave this open in case someone comes up with
one though, and to document the present best fix.  I will summarily
close future reports from people who didn't read it though ;-)

Cheers,
Ron




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to