Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 8 Jun 2019 11:32:46 -0700
From:      David Wolfskill <david@catwhisker.org>
To:        Adam Weinberger <adamw@freebsd.org>
Cc:        FreeBSD Ports <freebsd-ports@freebsd.org>
Subject:   Re: Cleaning up pkg-message
Message-ID:  <20190608183246.GI1170@albert.catwhisker.org>
In-Reply-To: <CAP7rwcgpDsTsnL0yE_JZMOfoiTzc0qM_LbKo=pmRpswWCvxShw@mail.gmail.com>
References:  <CAP7rwcgpDsTsnL0yE_JZMOfoiTzc0qM_LbKo=pmRpswWCvxShw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--HdWHc0xvClx/wAyb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jun 08, 2019 at 12:11:57PM -0600, Adam Weinberger wrote:
> Hello everyone,
>=20
> 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.
>=20
> pkg-message is shown to every user on every install. UPDATING is only
> shown when users run `pkg updating` *and* /usr/ports/UPDATING exists.
> I suspect that only a small proportion of users do that.

Well, for folks who install pre-built packages, probably.

For those of us who -- for at least some systems -- build from ports
locally, I'm less confident: I check it for relevant entries that
have been added since last time I updated installed ports on my
laptop or local build machine (which is daily) or my work desktop
(which is weekly).

Mind, its utility falls a bit short of the mark: ref.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227193

> pkg-message needs to contain only highly relevant information. Many,
> many ports have messages with irrelevant information that users are
> likely to get message fatigue and ignore them entirely. I don't want
> to pick on Joe Barbish, because his work is absolutely fantastic, but
> dns/dns2blackhole/pkg-message is an example of a giant message that
> tells users to do the same thing they always do for any port:
> ########################################################################
>=20
>                       dns2blackhole
>=20
>    Malware Prevention through Domain Blocking (Black Hole)
>=20
>    Issue "man dns2blackhole"  For configuration and usage information
>=20
> ########################################################################
>=20
> We now have the ability to specify messages that appear on initial
> install, or on upgrades from/to specific version. So here is what I
> propose as policy:
>=20
> >>>
> pkg-message must contain only information that is vital to setup and
> operation, and that is unique to the port in question. Setup
> information should only be shown on initial install, and upgrade
> instructions should be shown only when upgrading to the relevant
> version. All committers have blanket approval to constrain existing
> messages to install/upgrade ranges using the UCL format
> specifications. Message pruning falls under the blanket approval as
> well, but committers are encouraged to get maintainer input
> beforehand.
> <<<
>=20
> What are your thoughts?
> ....

No objections, and de-cluttering seems like a pretty good idea.  (At
least you didn't insert a requirement that any such messages must "spark
joy." :-) )

Peace,
david
--=20
David H. Wolfskill				david@catwhisker.org
"...including Mars (of which the Moon is a part)...." -- Donald J. Trump

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

--HdWHc0xvClx/wAyb
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAlz7/05fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy
OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2
Pck+wggApBLsonlsiaU3lCBQnt08DibPypdfOvNs/t4xmGM1onIgbGEkzNr3w4RC
WSu1n7T5QKpnv3DSIhjhRBBQyG8l9hnHJ7ZFZDKPoZmr+k/HIu71dai84a0VC9T+
OAByX5oFbIlhGCn757DwkA12KC64Jb6gLZZgyyCDfzXZvwnM3p6uKsWto+sFCZ2q
2dxhqq0dzYlke5OXr67Y8Ovos+QQKEIs82J/ivJ/ldVAu+qH7jH2B7uW/XIKH2Ba
kxp5tV1tN8YxzsMLaOFLdgXqXU4RLpUR8FILHOamygSMg5xkPzmVLvAmeUDUBto3
7Gm51RnqBd4ZJyGuzND38qwuZvMuBg==
=iyI4
-----END PGP SIGNATURE-----

--HdWHc0xvClx/wAyb--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190608183246.GI1170>