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 back to
a certain functionality (option) in another port
On Sat, Jun 8, 2019 at 12:29 PM Bob Eager wrote:
>
> On Sat, 8 Jun 2019 12:16:05 -0600
> Adam Weinberger 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
On Sat, Jun 08, 2019 at 12:11:57PM -0600, 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
On Sat, 8 Jun 2019 12:16:05 -0600
Adam Weinberger 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
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. UPDATING is only
shown when users run `pkg
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. UPDATING is only
shown when users run `pkg
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 back to
> a certain functionality (option) in another port (devel/binutils)
> missing.
>
> In pseudo-code this
In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237688 we had
a user report against lang/gcc* ports that could be traced back to
a certain functionality (option) in another port (devel/binutils)
missing.
In pseudo-code this could be addressed as follows in lang/gcc*
.if $(binutils built
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
