On 5/11/13, Andrea Venturoli wrote:
> On 05/10/13 15:50, b.f. wrote:
...
> Here's what I did:
> # find /usr/ports -type f -exec grep -l OPENSS_PORT "{}" ";"
>
> This showed very few ports really requiring openssl from ports, none of
> which I had cu
On 5/10/13, Andrea Venturoli wrote:
> On 05/10/13 14:32, b.f. wrote:
>
>>> Would I screw too many things if I tried adding:
>>>> WITH_OPENSSL_BASE=yes
>>
>> Yes, because then the additions to the check-depends target in
>> ports/Mk/bsd.openssl.mk would
Andrea wrote:
...
> I had a look at /usr/ports/net/openldap23-server/Makefile and only found:
> > USE_OPENSSL=yes
>
> AFAICT this does not give any preference wrt to base vs port openssl; if
> I'm correct this means the port is choosen if installed, but, otherwise,
> openssl from base
Ronald wrote:
...
> It occurs to me that *something*, i.e. some tool(s) within the FreeBSD
> panoply, *must* already be reading and/or otherwise making use of those
> MD5 checksums within the +CONTENTS files. Otherwise, why would they even
> be there? So my question really comes down to this: W
>I received a lot of complaint about ocaml being in a bad shape: lang/ocaml
>being
>outdated, lots of ocaml ports not being carefully maintained and updated.
>
>I personnally know nothing about ocaml so I'm not able to actually be helpful
>to
>improve the situation, I would love to see people tak
On 2/13/13, Anton Shterenlikht wrote:
> From s...@troutmask.apl.washington.edu Wed Feb 13 03:40:53 2013
>
> On Wed, Feb 13, 2013 at 02:15:08AM +, b.f. wrote:
> > On 2/13/13, Steve Kargl wrote:
> > > On Wed, Feb 13, 2013 at 12:1
> AN wrote:
...
This appears to be one of those unfortunate errors that sometimes
occur when the presence of additional software on your system
adversely affects a build, in a way that isn't seen on the test
machines or the package-building cluster, because those machines start
builds in a clean
On 2/8/13, Kimmo Paasiala wrote:
> On Fri, Feb 8, 2013 at 10:45 PM, Kimmo Paasiala wrote:
>> On Fri, Feb 8, 2013 at 10:17 PM, Anton Shterenlikht
>> wrote:
>>> From bf1...@googlemail.com Fri Feb 8 17:33:09 2013
>>>
>>> > > I don't think it's true.
>>> > > While still on
On 2/8/13, Anton Shterenlikht wrote:
> From bf1...@googlemail.com Fri Feb 8 17:33:09 2013
>
> > > I don't think it's true.
> > > While still on 9.1 ports, the latest
> > > entry in UPDATING was (well I lost it now)
> > > about NOV-2012. I believe the revision was
>On Wed, Jan 16, 2013 at 08:48:37AM +0000, b.f. wrote:
>> Mark wrote:
>> >On Wed, Jan 16, 2013 at 01:51:39AM +, RW wrote:
>> >> > Reports are sent to ports@ every 2 weeks.
>> >> And I wonder how many people read carefully through all 478 entries.
Mark wrote:
>On Wed, Jan 16, 2013 at 01:51:39AM +, RW wrote:
>> > Reports are sent to ports@ every 2 weeks.
>>
>> And I wonder how many people read carefully through all 478 entries.
>
>And your suggestion is ... ?
>
Try ports/ports-mgmt/portupdate-scan.
b.
___
> Building for acroreadwrapper-0.0.20110920
> Warning: Object directory not changed from original
> /usr/ports/print/acroreadwrapper/work/linux_adobe_kmod-20110920
> @ -> /usr/src/sys
> machine -> /usr/src/sys/i386/include
> x86 -> /usr/src/sys/x86/include
> gcc46 -O2 -pipe -march=pentium4 -mtune=p
Michael wrote:
>Dear FreeBSD community,
>
>2 months ago I submitted four port updates related to the
>ocaml/language. The PRs used to be listed by portsmon but I recently
>noticed they disappeared. [1]
>
>How can I help to let these changes go into our ports tree?
>
>
>The four PRs are
>
>2012/11/0
Lev wrote:
>
> Now, when some port after update installs new version of shared
> library, used by other ports, here are two variants:
>
> (a) To bump versions of all dependant ports (PORTREVISION=${PORTREVISION} +
> 1)
>
> (b) Don't touch other ports, but add copy'n'pasted item into
> UP
14 matches
Mail list logo
