[M3devel] upgrade.sh CFGD code seems wrong/dead?

[Jay]

I don't think the FHS matters here.
I don't want to get too far into the business
of supporting people (even admins) editing these files.
Nor do I want to avoid overwriting or merging their changes
for later releases.
 

Ideally, people should be as quick to edit cm3.cfg as
they are to edit any bash/perl/python in /usr or to rebuild
cm3 from source.
 

But that might not be possible.
There might also be decisions for which one size does not fit all.
It is easy to see that.
What cminstall used to prompt about are some where user /might/ want
a different choice, but which there are also defaults that suit
the majority of folks.
It is a little unclear.
Like, if postgres/odbc are in the location used by the platform's
port/package system, or did user get "upstream directly" and it
went in a different default like /usr/local? Or do they have a
custom install location?
 

Like, if they want to run a particular gcc by full path, or
if the first in $PATH is what they want? First in $PATH is certainly
very common, but so are other options, like gcc-version.
 
 
I guess, ideally, more of the code is moved into cm3, leaving
cm3.cfg really only for things people can edit freely.
 

 - Jay


----------------------------------------
> Date: Fri, 26 Jun 2009 10:01:44 +0200
> From: wagner at elegosoft.com
> To: jay.krell at cornell.edu
> CC: m3devel at elegosoft.com
> Subject: Re: upgrade.sh CFGD code seems wrong/dead?
>
> Quoting Jay :
>
>>
>> This block in upgrade.sh seems dead, given that nothing sets CFGD.
>>
>> Searching for 'CFGD'...
>> C:\dev2\cm3.2\scripts\upgrade.sh(95): cp -v ${f} ${CFGD}/${b}
>>
>>
>> if [ "${UPGRADE_CM3_CFG}" = "yes" -o "${ret}" != 0 ]; then (
>> ....
>>
>>
>> I'd like to move the config files to root/bin/config instead of
>> littering bin. Ok?
>
> No. This would just be another directory which does not conform to
> FSH standards. I already extended cm3 to search for config files
> in various /etc directories, though that's still untested.
>
> I'd prefer that we don't move config files _now_ before the release,
> but if you want to do it, test it:
>
> o move them to cm3/etc
> o test cm3 with that setup on at least one platform
> o adapt scripts for regression etc. as you deem necessary
> o watch tinderbox results and fix again ;-)
>
>>
>> This is one of the few places that is related to that.
>
> As for your question above, I cannot say without browsing and grepping
> the code which I cannot do from here (isolated network); perhaps tonight...
>
> Olaf
> --
> Olaf Wagner -- elego Software Solutions GmbH
> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>