Screwed ports tree/package database on my server

[Matt Sealey]

Ooh great!

That fixed it. I must have set it because some packages were depending on
Apache 2.0 and it was being installed concurrently (and stuff stopped working
at that point as it was going to the wrong port..)

Now it's unset it is registering packages properly.

Thanks.

I'd like to know why Apache 2.0 ever got reinstalled though, in the first
place.. but I hope it simply doesn't happen again so I won't have to worry.

-- 
Matt Sealey <matt at genesi-usa.com>
Manager, Genesi, Developer Relations
 

> -----Original Message-----
> From: Sam Lawrance [mailto:boris at brooknet.com.au] 
> Sent: Wednesday, May 31, 2006 7:02 AM
> To: matt at genesi-usa.com
> Cc: freebsd-ports at freebsd.org
> Subject: Re: Screwed ports tree/package database on my server
> 
> 
> On 31/05/2006, at 9:56 PM, Matt Sealey wrote:
> 
> >
> >> Do you have any thing set in /etc/make.conf?  Sometimes 
> this kind of 
> >> problem can be caused by misusing some internal ports variables.
> >
> >
> > USE_APACHE=2.2
> >
> 
> This is probably where all your damage is coming from.  
> USE_APACHE is  
> an internal variable, to be set by ports only.  By setting it in  
> make.conf, every port you install gets a dependency on Apache 2.2.
> 
> Another side effect is that apache 2.2 then depends on itself (a  
> circular dependency), which is why you end up with thousands of make  
> processes .
> 
>