On 08/06/2019 19:29, Bob Eager wrote:
> The committer folded the README file into pkg-message, and I disagree
> with this:
> 2) It meant that an end user (without access to the ports tree) didn't
> have an immediate way to see the README contents.
That's not actually correct.
```
% pkg info -D p
On 08/06/2019 19:11, Adam Weinberger wrote:
Hello everyone,
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.
pkg-message is shown to every user on every install. UP
Grzegorz Junka wrote on 2019/06/09 16:12:
On 08/06/2019 19:11, Adam Weinberger wrote:
Hello everyone,
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.
pkg-message i
On 09/06/2019 15:44, Miroslav Lachman wrote:
Grzegorz Junka wrote on 2019/06/09 16:12:
On 08/06/2019 19:11, Adam Weinberger wrote:
Hello everyone,
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,
On Sat, Jun 8, 2019 at 11:00 PM Mel Pilgrim
wrote:
>
> On 2019-06-08 9:57, Adam Weinberger wrote:
> > On Sat, Jun 8, 2019 at 10:02 AM Gerald Pfeifer wrote:
> >>
> >> In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237688 we had
> >> a user report against lang/gcc* ports that could be traced
On Sun, Jun 9, 2019 at 9:33 AM Grzegorz Junka wrote:
>
>
> On 09/06/2019 15:44, Miroslav Lachman wrote:
> > Grzegorz Junka wrote on 2019/06/09 16:12:
> >>
> >> On 08/06/2019 19:11, Adam Weinberger wrote:
> >>> Hello everyone,
> >>>
> >>> I want to get some stakeholder input on our pkg-message file
On 09/06/2019 16:55, Adam Weinberger wrote:
On Sun, Jun 9, 2019 at 9:33 AM Grzegorz Junka wrote:
On 09/06/2019 15:44, Miroslav Lachman wrote:
Grzegorz Junka wrote on 2019/06/09 16:12:
On 08/06/2019 19:11, Adam Weinberger wrote:
Hello everyone,
I want to get some stakeholder input on our p
On 9 Jun2019, at 09:33, Grzegorz Junka wrote:
> Because pkg doesn't know if it's a first install or reinstall.
This is a solvable issue, however. There are may things that could be checked
to see if this is a new install or not, though some go them will require some
additional tracking pf [por
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 9 Jun 2019 12:52:41 +0100
Matthew Seaman wrote:
> On 08/06/2019 19:29, Bob Eager wrote:
> > The committer folded the README file into pkg-message, and I
> > disagree with this:
>
> > 2) It meant that an end user (without access to the po
