apache2 location

[Bradley Giesbrecht]

On Mar 1, 2009, at 4:39 PM, Ryan Schmidt wrote:

> On Mar 1, 2009, at 11:39, Bradley Giesbrecht wrote:
>
>> On Mar 1, 2009, at 3:34 AM, Ryan Schmidt wrote:
>>
>>> On Mar 1, 2009, at 03:58, Scott Haneda wrote:
>>>> On Feb 28, 2009, at 3:55 PM, Ryan Schmidt wrote:
>>>>> $ port installed apache*
>>>>> The following ports are currently installed:
>>>>> apache @1.3.41_0
>>>>> apache2 @2.2.11_0 (active)
>>>>> $ port activate apache @1.3.41_0
>>>>> --->  Activating apache @1.3.41_0
>>>>> Error: port activate failed: Image error: /mp/share/man/man1/ 
>>>>> dbmmanage.1.gz is being used by the active apache2 port.  Please  
>>>>> deactivate this port first, or use the -f flag to force the  
>>>>> activation.
>>>>> $
>>>>
>>>> Why does ports care if a man page is shared?  I do not really  
>>>> even consider it in use.  Forgive my lack of understanding, and  
>>>> hopefully no one jumps my butt on this idea...
>>>>
>>>> Why are man pages part of the process of being registered as  
>>>> activated? It is a man page, not a binary.  Maybe man pages  
>>>> should just not be part of this entire chain of checks.
>>>
>>> MacPorts has no special knowledge at destroot time that this is a  
>>> manpage. It treats all files the same.
>>>
>>> All files need to be part of the destroot and registered to the  
>>> port so that "port contents" can show them and "port uninstall"  
>>> can uninstall them.
>>>
>>> You wouldn't want an older manpage provided with the apache (1)  
>>> port to silently overwrite the newer manpage you already had from  
>>> the apache2 port. These are the kinds of problems having a  
>>> destroot solves.
>>
>> 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.
>
> It is not possible with MacPorts today because of the conflicting  
> files.
> Well, it would be possible if someone forced the activation of one  
> apache after installing the other, but we strongly discourage users  
> from using the force option.
>
>> Shouldn't they just be conflicted so you have to uninstall apache  
>> to get apache2.
>
> They do conflict because they want to write the same files. To get  
> apache2 if you already have apache, you need to deactivate apache  
> and then activate apache2. Or activate apache2 forcibly, which is  
> not recommended.

>> As for perl5, why do p5 man pages exist for yet to be installed p5  
>> modules?
>> Is that normal on other systems?
>
> I'm not sure what you mean. Can you give an example?

I'll reinstall mports and give you some examples. I can't recall now  
but I have seen it.

>> How about moving collisions instead of over writing?
>>
>> /opt/local/var/macports/collisions/[datetime]/opt/local/share/man/ 
>> [existing-file]
>
> In fact, they do get moved. The old files get an extension ".mp_$ 
> {timestamp}"

I've noticed that. Moving them under a common dir would allow periodic  
cleanup to come into play without traversing the tree.
Maybe /opt/local/var/macports/collisions/opt_local_share_man_[existing- 
file]_[datetime] would be even better.

//Brad