Cleaning up pkg-message

[Adam Weinberger]

On Sat, Jun 8, 2019 at 12:29 PM Bob Eager <rde at tavi.co.uk> wrote:
>
> On Sat, 8 Jun 2019 12:16:05 -0600
> Adam Weinberger <adamw at adamw.org> wrote:
>
> > I want to get some stakeholder input on our pkg-message files. I think
> > we need to have a clear policy about what does and doesn't belong in
> > them, and I'd like to get your input.
>
> I agree.
>
> I recently noticed that one of my ports had been modified by the
> previous committer. I had a pkg-message which was short and contained
> concise, minimal information. I also has a README file, installed
> in /usr/local/share/doc/... if the DOCS option was selected.
>
> The committer folded the README file into pkg-message, and I disagree
> with this:
>
> 1) It added far too much bulk to pkg-message.
>
> 2) It meant that an end user (without access to the ports tree) didn't
> have an immediate way to see the README contents.
>
> 3) The committer tacked the README file onto pkg-message without
> noticing that there was a %%DOCSDIR%% to be expanded, so that is how it
> appears in pkg-message.

Committers have the prerogative to alter pkg-message as required, but
as the maintainer you have every right to object. Which port is it?
I'd be happy to fix that for you.

# Adam


-- 
Adam Weinberger
adamw at adamw.org
https://www.adamw.org