[csw-maintainers] Adjusting $(DIRPATHS) for sparse zones support with shared /opt

Philip Brown phil at bolthole.com
Fri Jun 19 19:40:24 CEST 2009


On Fri, Jun 19, 2009 at 12:11:10PM -0500, Mike Watters wrote:
> > You want firefox to have all its default configs in /etc? Individually? 
> > For every machine?
> > 
> > I dooont think sooo....
> > You want global configs for a beast like that.
> 
> Firefox is a different beast, and by default does not store anything in *etc*
> the global configs for firefox are stored in .*/share and the "local configs"
> are stored in the user's home directory under .mozilla

but it could.
And in some ways, it "should". It just doesnt at the moment :-)

> 
> I would say that firefox is not an issue in sharing /opt.
> 
> Software like xpdf, I don't think it matters where the configs are located
> since they normally don't change.

So, you seem to be agreeing with my premise, that SOME programs are fine in
having their configs on the global /opt/csw, when they dont change.



> the whole problem here, I believe, is how do we make CSW packages respect both
> local configs and global configs without hacking up every piece of software we
> package.

We simply cant do that for *every* package.  more below.


> ....
> This would solve the issue, although I reiterate this is not the best solution,
> but I am not sure there is a "best solution" with this problem.

I believe that is the core truth here. There is no
"one size fits all 'best' solution".

 What we CAN do, is try to make the "best" choice, on a package-by-package
basis. with certain guidelines.

The most relevant ones being,
 "treat /opt/csw/* as read-only after install. If something is likely to
  need significant changing after initial install, then it belongs in
  /etc/opt/csw or /var/opt/csw"




More information about the maintainers mailing list