Christian Weisgerber wrote on 2017/06/07 22:18:
What is the naming convention for etc/periodic/*/* files installed
by ports?
Looking over the ports tree, I see that most adhere to the
NNN.*name* pattern also used in the base system, although it's
unclear how the NNN numbers are assigned and the
On 6/7/2017 1:18 PM, Christian Weisgerber wrote:
> What is the naming convention for etc/periodic/*/* files installed
> by ports?
>
> Looking over the ports tree, I see that most adhere to the
> NNN.*name* pattern also used in the base system, although it's
> unclear how the NNN numbers are
On 07/06/2017 16:18, Christian Weisgerber wrote:
> What is the naming convention for etc/periodic/*/* files installed
> by ports?
>
> Looking over the ports tree, I see that most adhere to the
> NNN.*name* pattern also used in the base system, although it's
> unclear how the NNN numbers are
What is the naming convention for etc/periodic/*/* files installed
by ports?
Looking over the ports tree, I see that most adhere to the
NNN.*name* pattern also used in the base system, although it's
unclear how the NNN numbers are assigned and the rest of the name
is somewhat flexible.
The lone
On 06/06/2017 04:00 AM, Torsten Zuehlsdorff wrote:
> Aloha,
>
>> I noticed that ports head has had security updates for PostgreSQL 9.2 to
>> 9.6 since 11 May, but these haven't been merged into the 2017Q2
>> branch.The last batch of updates in February arrived into 2017Q2 the
>> same day as the
Hi,
I tried building Firefox today and got stuck with this error:
/usr/ports/www/firefox/work/firefox-53.0.3/obj-x86_64-unknown-freebsd10.1/dist/include/js/RootingAPI.h:837:5:
error: 'JS::Rooted::Rooted(const JS::Rooted&) [with T =
JSObject*]' is private
Rooted(const Rooted&) = delete;
and
Hi ports@
It might amuse someone to port this, it's in C for MS at present.
http://ollydbg.de/Paperbak/#1
Article & discussion here:
https://blog.codinghorror.com/the-paper-data-storage-option/
I'm not asking for it to be ported, just it's not in our ports/
& may interest some.
What is the status of gcc-aux (5 and 6) on FreeBSD-current following the
introduction of 64-bit inodes?
It was broken, so I read from the emailing list, but is it still broken?
No indication of being broken in PORTSDIR/lang/gcc6-aux or gcc5-aux.
Tom
