FreeBSD ports you maintain which are out of date

2015-07-15 Thread portscout
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

Re: www/squid's cache dir

2015-07-15 Thread RW via freebsd-ports
On Tue, 14 Jul 2015 21:39:39 -0700 (MST) timp wrote: > > Squid can use more than one cache directory, so it makes sense to > > have the default cache directory as a sub-directory of squid/. > > Additional cache dirs can be created manually by user in /var/squid, I > agree. Like /var/squid/cach

Re: www/squid's cache dir

2015-07-15 Thread timp
Ok, so you don't see the difference too, do you? The point is get rid of dirs which we don't really need for this port, and place cache to suitable dir which is made in base system for such purposes. Just for order. You think it's bad idea? 2015-07-15 14:08 GMT+03:00 freebsd-ports mailing list [vi

Re: Can't use nmap on 10.1

2015-07-15 Thread Andrea Venturoli
On 07/15/15 11:56, Andrea Venturoli wrote: I'll try enabling IPv6 in the kernel to see if that makes any difference and eventually I'll file a bug report. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201583 bye & Thanks av. ___ freebsd

Re: www/squid's cache dir

2015-07-15 Thread RW via freebsd-ports
On Wed, 15 Jul 2015 04:25:56 -0700 (MST) timp wrote: > Ok, so you don't see the difference too, do you? Actually I do see the difference - I think the current layout is better. My point was that "I can't see any difference" isn't a good argument for making disruptive change. I think it's obvio

Re: www/squid's cache dir

2015-07-15 Thread timp
> > Ok, so you don't see the difference too, do you? > > Actually I do see the difference - I think the current layout is > better. My point was that "I can't see any difference" isn't a good > argument for making disruptive change. > > > I think it's obvious that putting multiple caches unde

FreeBSD Port: devel/cmake - cannot build without py-babel

2015-07-15 Thread Miroslav Lachman
Hi, cmake cannot be built in my poudriere setup. It always ends with the same error (on FreeBSD 8.4 and 10.1) [ 99%] Building CXX object Source/CMakeFiles/cpack.dir/CPack/cpack.cxx.o Linking CXX executable ../bin/cpack [ 99%] Built target cpack Scanning dependencies of target ctest [ 99%] Build

Re: FreeBSD Port: devel/cmake - cannot build without py-babel

2015-07-15 Thread Kris Moore
On 07/15/2015 10:57, Miroslav Lachman wrote: > Hi, > cmake cannot be built in my poudriere setup. It always ends with the > same error (on FreeBSD 8.4 and 10.1) > > [ 99%] Building CXX object Source/CMakeFiles/cpack.dir/CPack/cpack.cxx.o > Linking CXX executable ../bin/cpack > [ 99%] Built target c

Re: www/squid's cache dir

2015-07-15 Thread Nick Rogers
On Wed, Jul 15, 2015 at 7:33 AM, timp wrote: > > > Ok, so you don't see the difference too, do you? > > > > Actually I do see the difference - I think the current layout is > > better. My point was that "I can't see any difference" isn't a good > > argument for making disruptive change. > > > > >

Re: FreeBSD Port: devel/cmake - cannot build without py-babel

2015-07-15 Thread Miroslav Lachman
Kris Moore wrote on 07/15/2015 17:27: On 07/15/2015 10:57, Miroslav Lachman wrote: The full log is here http://pastebin.com/5MxnT3K5 It worked two weeks ago without babel. Now Sphinx (py27-Jinja2) requires Babel extension. Is this intentional? Miroslav Lachman Yea, the update to sphinx

poudriere with custom packages

2015-07-15 Thread Aristedes Maniatis
I have a custom built package which I'm building outside the FreeBSD ports system (using pkg-create commands). How can I add that package to a poudriere managed repository so that it appears in the package index and can be easily installed like any other package? Thanks for any help Cheers Ari

WARNING: 'automake-1.14' is missing on your system.

2015-07-15 Thread O. Hartmann
Trying to perform building a port, I receive on several ports I'm about to propose a nasty, sticky error and I can not fathom where it is rooted. For one proposed port, devel/ocl-icd, please refer to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181244 which contains on the very last few com