Another possible way is "watch" the ports you maintained with
FreshPorts: https://www.freshports.org/
Li-Wen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
bob prohaska fbsd at www.zefox.net wrote on
Mon May 17 23:46:38 UTC 2021 :
> On Mon, May 17, 2021 at 12:28:24PM -0700, Mark Millard via freebsd-ports
> wrote:
> > bob prohaska fbsd at www.zefox.net wrote on
> > Mon May 17 15:55:21 UTC 2021 :
> >
> > > The existing conflict between versions of
On 2021-05-17 18:17, Julian H. Stacey wrote:
Chris wrote:
On 2021-05-17 16:30, Jan Beich wrote:
> Chris writes:
>
>> I'd like to subscribe to the commit messages
>> ( dev-commits-ports-all )
>> but only receive messages that affect me -- the
>> ports I currently maintain. Is it possible? Or
>>
On Tue, 18 May 2021, Julian H. Stacey wrote:
I'd use /usr/ports/mail/procmail
I wouldn't; it's an unsupported and obscure scripting language just asking
for bugs, and actually has several CVEs against it.
Better filters exist, such as "sieve" etc.
-- Dave
Chris wrote:
> On 2021-05-17 16:30, Jan Beich wrote:
> > Chris writes:
> >
> >> I'd like to subscribe to the commit messages
> >> ( dev-commits-ports-all )
> >> but only receive messages that affect me -- the
> >> ports I currently maintain. Is it possible? Or
> >> am I just dreaming? ;-)
> >
>
On 2021-05-17 16:30, Jan Beich wrote:
Chris writes:
I'd like to subscribe to the commit messages
( dev-commits-ports-all )
but only receive messages that affect me -- the
ports I currently maintain. Is it possible? Or
am I just dreaming? ;-)
No clue but I use Herald rules for something
On Mon, May 17, 2021 at 12:28:24PM -0700, Mark Millard via freebsd-ports wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Mon May 17 15:55:21 UTC 2021 :
>
> > The existing conflict between versions of python strikes me as more of a
> > planning problem than a software bug. It may be naive,
Chris writes:
> I'd like to subscribe to the commit messages
> ( dev-commits-ports-all )
> but only receive messages that affect me -- the
> ports I currently maintain. Is it possible? Or
> am I just dreaming? ;-)
No clue but I use Herald rules for something similar.
Alexis Praga writes:
> Hi guys,
>
> Thanks to Li-Wen Hsu [1], I now know the new version does not build on 11.4
> with :
> /usr/bin/ld: unrecognized option '-plugin'
> Which seems due to the '-flto' flag according to this issue :
>
I'd like to subscribe to the commit messages
( dev-commits-ports-all )
but only receive messages that affect me -- the
ports I currently maintain. Is it possible? Or
am I just dreaming? ;-)
Thanks in advance for any insight into this.
--Chris
___
bob prohaska fbsd at www.zefox.net wrote on
Mon May 17 15:55:21 UTC 2021 :
> The existing conflict between versions of python strikes me as more of a
> planning problem than a software bug. It may be naive, but I don't see
> why python37 and python38 can't use distinct names for files placed in
Hi guys,
Thanks to Li-Wen Hsu [1], I now know the new version does not build on 11.4
with :
/usr/bin/ld: unrecognized option '-plugin'
Which seems due to the '-flto' flag according to this issue :
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230137
I've tried the fix mentioned
On Mon, May 17, 2021 at 09:37:07AM -0400, George Mitchell wrote:
> On 5/16/21 10:19 PM, bob prohaska wrote:
> > [...]
> > I'd like to see the ports system keep working as it has in the past, but
> > that seemingly
> > requires a kind of machine intelligence that hasn't evolved yet. Poudriere
> >
On 5/16/21 10:19 PM, bob prohaska wrote:
[...]
I'd like to see the ports system keep working as it has in the past, but that
seemingly
requires a kind of machine intelligence that hasn't evolved yet. Poudriere
seems like
a brute force approach. [...]
You'll find quite a few remaining fans of
Hi all,
I've rewritten the suggested port for kitty which was waiting here :
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233010.
With newer versions, porting is much easier and I have a functional
kitty on my system.
As I'm new to porting files, any guidance or advice is appreciated.
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,
On Mon, May 17, 2021 at 04:44:04AM +, Thomas Mueller wrote:
>
> My question, Bob, is, if you are dissatisfied with poudriere, what do you use
> for FreeBSD ports?
I'm not dissatisfied, I'm overwhelmed.
Usually, a simple
make -DBATCH > make.log &
works.
hth,
bob prohaska
17 matches
Mail list logo
