On 13.11.21 15:51, Daniel Engberg wrote:
I agree that old doesn't necessarily mean it's useless
Noted!
however we do need to prune the ports from time to time
Why? Why do we need to "prune the ports from time to time"? I'm aware of
one principle, under which a port can be deleted: the port
In the following output from poudriere-devel there is no report
of devel/llvm13 in [02] being "Finished" or [02] starting
devel/qt5-help but there is a report of [02] finishing
devel/qt5-help . The "Built ports" list does include devel/llvm13 .
. . .
load: 32.63 cmd: sh 40873 [runnable] 0.01r 0
On 2021-Nov-15, at 11:35, Mark Millard wrote:
> On 2021-Nov-15, at 10:40, Dimitry Andric wrote:
>
>> On 15 Nov 2021, at 19:14, Mark Millard via arm wrote:
>>>
>>> There error was:
>>>
>>> error: non-constant-expression cannot be narrowed from type 'long long' to
>>> 'std::size_t' (aka 'u
On 2021-Nov-15, at 10:40, Dimitry Andric wrote:
> On 15 Nov 2021, at 19:14, Mark Millard via arm wrote:
>>
>> There error was:
>>
>> error: non-constant-expression cannot be narrowed from type 'long long' to
>> 'std::size_t' (aka 'unsi
>> gned int') in initializer list [-Wc++11-narrowing]
>>
On 15 Nov 2021, at 19:14, Mark Millard via arm wrote:
>
> There error was:
>
> error: non-constant-expression cannot be narrowed from type 'long long' to
> 'std::size_t' (aka 'unsi
> gned int') in initializer list [-Wc++11-narrowing]
> std::size_t resultBytes{size * elementBytes};
>
There error was:
error: non-constant-expression cannot be narrowed from type 'long long' to
'std::size_t' (aka 'unsi
gned int') in initializer list [-Wc++11-narrowing]
std::size_t resultBytes{size * elementBytes};
^~~
/wrkdirs/usr/ports/devel/llvm13/wor
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, you
On 15/11/21 12:01, Ronald Klop via freebsd-ports wrote:
Van: Rob LA LAU
Datum: zondag, 14 november 2021 16:56
Aan: ronald-li...@klop.ws, freebsd-po...@freebsd.org
Onderwerp: Re: Adding functionality to a port
Thanks Ronald. But I'm not asking how or where to report bugs.
Allow me to rephrase
Van: Rob LA LAU
Datum: zondag, 14 november 2021 16:56
Aan: ronald-li...@klop.ws, freebsd-po...@freebsd.org
Onderwerp: Re: Adding functionality to a port
Thanks Ronald. But I'm not asking how or where to report bugs.
Allow me to rephrase my question.
If and when I am a FreeBSD port maintainer
On 15/11/21 09:42, Rob LA LAU wrote:
Hi,
On 14/11/2021 20:49, Guido Falsi wrote:
You talk about "adding a periodic script". That is not even a real
modification to the upstream software IMHO. Just adding some glue code
for FreeBSD. If the script does what it advertises, and has no
malicious i
Hi,
On 14/11/2021 20:49, Guido Falsi wrote:
You talk about "adding a periodic script". That is not even a real
modification to the upstream software IMHO. Just adding some glue code
for FreeBSD. If the script does what it advertises, and has no malicious
intent I see nothing wrong with it. If
11 matches
Mail list logo
