[M3commit] CVS Update: cm3

[Olaf Wagner]

I can live with a cm3-local.cfg file which gets included when it exists,
contains local overrides and is never touched by he installation.

We have to be careful to backup existing configs and informing the
users before the installation though.

I think upgrade did backups of the config, too.

Can you check the scripts in the release branch if anything needs
to be merged back? I won't be able to do that today.

Olaf

Quoting Jay K <jay.krell at cornell.edu>:

> I thought it was too, before I looked at it.
> Could be that head and release are very divergent.
> I didn't look at release, oops.
>   I probably will "soon".
>
>
> The config files are "partly part of the compiler", and partly   
> system-specific.
>  So they might have to be updated with the compiler.
>
>
> Perhaps we can have cm3.cfg.user or cm3.cfg.local, that we never edit,
> and maybe we should constrain it, like very line
> must have an equals sign, and if it has a percent, percent must   
> follow equals.
>
>
> e.g.
> m3back_flags = "-custom"
> SYSTEM_CC = "custom" % comment blah blah
> SYSTEM_LIBS{"LIBC"} = "custom"
> SYSTEM_LIBORDER += [custom]
>
> But that might not be flexible enough.
>
> Another option is that cm3.cfg file do like:
> if exists("cm3.cfg.user.first")
>   include("cm3.cfg.user.first")
> end
> ...
> if exists("cm3.cfg.user.last")
>
>   include("cm3.cfg.user.last
>
> end
>
>
>
> which is infinitely flexible and not well defined.
>  Even limiting to assignments is not well defined.
>  You know, there's an interface somewhere in there, but it isn't   
> well specified. My fault.
>   I let things evolve and get discovered gradually, sometimes hard   
> to know ahead of time what the result will be.
>  
>
> I've made changes since 5.8.6 released such that config files from   
> prior to 5.8.6 will not suffice.
> I can undo that, but there is an important policy and architecture question.
>
>
>  - Jay
>
> ----------------------------------------
>> Date: Thu, 22 Jul 2010 08:53:23 +0200
>> From: wagner at elegosoft.com
>> To: m3commit at elegosoft.com
>> Subject: Re: [M3commit] CVS Update: cm3
>>
>> Quoting Jay K :
>>
>> > I've manually updated the config files on SPARC32_LINUX Hudson node
>> > to try to fix this.
>>
>> That should be done by the upgrade script (and it already was AFAIR).
>> I wouldn't like the script shipping a newly built compiler to
>> unconditionally overwrite all my local configuration.
>>
>> Olaf
>>
>> >
>> >  - Jay
>> >
>> > ----------------------------------------
>> >> Date: Wed, 21 Jul 2010 17:53:14 +0000
>> >> To: m3commit at elegosoft.com
>> >> From: jkrell at elego.de
>> >> Subject: [M3commit] CVS Update: cm3
>> >>
>> >> CVSROOT: /usr/cvs
>> >> Changes by: jkrell at birch. 10/07/21 17:53:14
>> >>
>> >> Modified files:
>> >> cm3/scripts/: install-cm3-compiler.sh
>> >>
>> >> Log message:
>> >> upgrade config files when upgrading compiler
>> >>
>> >
>>
>>
>>
>> --
>> 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
>>
>



-- 
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