pkgsrc-WIP-changes archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: cannonball: Add a MESSAGE banner post-install with instructions to the place to copy ROMs. Suggested by nia@
- To: Leonardo Taccari <leot%NetBSD.org@localhost>
- Subject: Re: cannonball: Add a MESSAGE banner post-install with instructions to the place to copy ROMs. Suggested by nia@
- From: Greg Troxel <gdt%lexort.com@localhost>
- Date: Mon, 10 Jun 2019 12:09:02 -0400
Leonardo Taccari <leot%NetBSD.org@localhost> writes:
> Apart that, with MESSAGE it is clear that these instructions were added
> by pkgsrc maintainers while by adding README in share/doc/<package> it
> seems like that file is part of the official documentation.
Perhaps, but there should be almost no need for pkgsrc-specific
per-package documentation; we should be packaging hte program and its
documentation provided by upstream. The real problem in many cases is
that upstreams do not have adequate user documentation. So adding
something that feels like upstream's documentation is fine - it's much
like patching any other bug.
I think if we had 5% of the MESSAGE files we do now, and there were not
MESSAGE files that told people to enable things in rc.conf and to read
the upstream documentation, it would not be such an issue. But we have
a lot of things that I think are just annoying noise.
I think part of it is that sometimes when people package things, they
think their thing is more important than the other 18K. I see this on
upstream mailinglists all the time where they expect users to read and
follow non-standard build procedures instead of viewing it as upstream's
job to conform to norms to ease packaging.
That said, I will take a look at the guide and make sure the
explanations of where to look for documentation are there, as I suspect
that's underdocumented.
Home |
Main Index |
Thread Index |
Old Index