On Fri, Apr 13, 2007 at 07:04:38PM -0400, Joey Hess wrote:
> A package in main that causes cron to spew these messages unless a package
> in contrib is installed, is broken. Not installing Suggests is not intended
> to leave the system in this kind of state.

Fair comments, I don't disagree with that.

> mandb: warning: /usr/share/man/man1/i586-mingw32msvc-gcc-3.4.5.1.gz is a 
> dangling symlink
> 
> It would be acceptable to replace these symlinks with short man pages
> that point to cpp(1) etc for detailed documentation.

Policy is probably ok with that, but with the benefit of more time to
think on this, I'm not sure that I am.  Not having free documentation
for our primary toolchain _is_ a serious bug IMO.  So I think I'm leaning
toward the 'purge the symlinks and retitle this bug "binary w/o a manpage"'
solution, in preference to the 'cover the gaps, close the bugs, pretend its
all ok' path.

I'm sure we'll have free documentation again eventually.  I just don't
know when.  This really is an open issue (and a pita) until we do...

The bug can remain open as a reminder to all, it will just be a little
less annoying on a daily basis than the present solution.  Most people
using the toolchain can probably map foo-gcc to gcc(1) in their heads
without too much prompting, and it would probably be a safe bet the
majority already do rather than typing the full foo- alias.

If I'm still convinced of this at the next upload, that's what I'll do
then ...

> In the meantime, I'm purging this package. :-/

If you really need it in the meantime, rm works on these symlinks the
same as for any other broken package that left them dangling or forgot
them in a purge.  ; )


Thanks for your input just the same, its hard to judge lesser evils from
just a small sample of opinions.  In hindsight I agree the convenience to
people who do install the non-free docs does not balance the inconvenience
to those who don't with the present arrangement.

Cheers!
Ron




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

Reply via email to