Jyri Virkki wrote:
> Seema Alevoor wrote:
>   
>>> IIRC you mentioned sometime before that the contents of this build
>>> directory are static (only delivered by the OS install/upgrade, cannot
>>> change otherwise). If so, then /usr/apache2/build/ makes sense to me.
>>>       
>> Yes. These files are used by other scripts like apxs. User is not
>> expected to modify these files. These files contain the data related
>> to the Apache build environment.
>>     
>
> In that case it sounds like /usr... is the right place for both reasons.
>   
>
>   
>>> Do you know why it ended up in /var/apache2/build originally? Was that
>>> just a mistake?
>>>       
>> I don't know the reason why the build directory was placed under
>> /var/apache2 directory.  Stefan, do you know the reason ?
>>     
>
> I just read through the materials and discussion of the previous
> apache2 case (2004/676) and there isn't any coverage of the build
> directory, it just showed up under /var.  I'll check if the submitter
> of that case has any recollection about this topic.
>   

Where does apxs put things when built?  One issue here is that of 
Solaris zones.  Whatever is done, it should behave properly with respect 
to zones, right?  

This, by the way, if I recall correctly was one of the motivators for 
Cool Stack 1.1 to move to /opt from /usr/local.  I can't speak for the 
/usr/local decision in the first place, but I suspect it was to be 
fairly compatible with what most downloads want to do when you 
./configure them.

Well, now I've just tried it, and by default it will put things in the 
libexecdir, which in config_vars.mk is set to /usr/apache2/libexec (at 
least with the package currently in SFWNV).

So, perhaps the build directory (which seems to have things for building 
software, but not built software) needs to be in /usr but there should 
be a libexec which apxs should know how to use in /var/apache2/libexec.

Is there a good place to file CRs on this sort of thing so these issues 
don't get lost?

- Matt

-- 
Matt Ingenthron - Web Infrastructure Solutions Architect
Sun Microsystems, Inc. - Global Systems Practice
http://blogs.sun.com/mingenthron/
email: matt.ingenthron at sun.com             Phone: 310-242-6439


Reply via email to