apache2 location

[Bradley Giesbrecht]

On Mar 1, 2009, at 3:33 PM, Scott Haneda wrote:

> On Mar 1, 2009, at 9:39 AM, Bradley Giesbrecht wrote:
>
>> Is it very common to have apache and apache2 installed at the same  
>> time?
>> Looks like they conflict to me. They write the same files.
>> Shouldn't they just be conflicted so you have to uninstall apache  
>> to get apache2.
>>
>> As for perl5, why do p5 man pages exist for yet to be installed p5  
>> modules?
>> Is that normal on other systems?
>>
>> How about moving collisions instead of over writing?
>>
>> /opt/local/var/macports/collisions/[datetime]/opt/local/share/man/ 
>> [existing-file]
>
>
> Good idea...
> Also, where does MacPorts get the man pages from?  Maybe they should  
> just all be removed, then only the new ones get installed as you  
> need them when you add in a p5?
>
> Can I simply rm all the perl man pages, new ones will come in when I  
> instal something?

Unless someone perl wise explains why they need to be there in the  
first place it's a flaw in the port that put them there.

Where do they come from?

I'm going to wipe /opt and do a clean install to find out.

Something is clearly wrong.

Is it true that if I want to install assp as an example, and assp  
relies on p5-z thru p5-z, and I call port like so "port -f install  
assp" that the -f flag does not apply to the deps?

If so, then I have to install all the failed p5 deps by hand with -f.

If not, holy cow. I just ran -f on a whole chain of installs.


//Brad