Hi Zdenek,

I will now wait for another review of rd4 (At least Paul wanted to have another 
look at it), and then integrate your suggestions with the others to come into a 
rd5 for final final review.

>> HM. Do you really mean to set --sysconfigdir=/etc or rather 
>> --sysconfigdir=/etc/pgsql/8.3 ? I'd prefer the latter, as I believe 
>> having a default dir for each (major) version is a natural consequence 
>> of having a basedir for each (major) version.
> 
> By discussion with Peter this is version independent file. It means 
> there is no reason to have different directory. I prefer /etc/postgres, 
> but see my comments bellow.
> 
>> Why exactly do you want to avoid adding the root package and putting 
>> the sample config into the proper directory? Why is this "too big 
>> effort"? I'd write the ARC case if this is your concern.
> 
> ARC case is one problem. But main reason is to be sync with S10 
> packages. It is why I have been thinking to postpone this to the 8.4 
> integration. We cannot change it for S10. Only what I can do is 
> correctly set --syconfigdir to /etc.

OK. Though I don't understand why a patch can't introduce a package or what 
else 
the specific issues with s10 are, I'll

- remove the additional package
- put the sample config file back to where it was unter /usr/postgres
- use --sysconfigdir=/etc

But please note that if this is integrated, users would need to get informed 
about the change of the sysconfigdir. An s10 patch should probably look for 
/usr/postgres/8.3/psqlrc* files (except the sample) and move them to /etc.

>>> By the way not only Solaris has this issue. I checked SUSE and it has 
>>> similar problem.
>>
>> Yes, but SUSE does not offer official support for diskless clients 
>> while Sun does for Solaris. Also, Sun claims to go for the "right 
>> solution" first, so I think others not implementing proper file system 
>> layouts should not be an excuse.
> 
> I was only example that there is not consensus how to do it.

Agree. Sorry if I have overreacted on this.

Nils


Reply via email to