[Bug 1001632] Patch for making it easy to diff ecos configurations

[Bug 1001632] Patch for making it easy to diff ecos configurations

[bugzilla-daemon]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001632

John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO
                 CC|                            |john@dallaway.org.uk
         AssignedTo|unassigned@bugs.ecos.source |john@dallaway.org.uk
                   |ware.org                    |
     Ever Confirmed|0                           |1

--- Comment #4 from John Dallaway <john@dallaway.org.uk> 2012-08-01 20:40:24 BST ---
Hi Martin

Thank you for your contribution. I like the idea of a dump command that emits 1
line per CDL item for use with diff and other tools.

I think the format of each line could be improved because:

a) The active/inactive state of a CDL item is distinct from its value and it
seems good to reinforce that distinction in the line format.

b) It can be important to know when the value _source_ (default/inferred/user)
has changed, even if the value has not changed.

My suggested line format, by example, is as follows:

component CYGPKG_MY_COMPONENT active bool default 1
option CYGSEM_MY_OPTION inactive
option CYGOPT_BOOL_OPTION active bool user 0
option CYGOPT_BOOLDATA_OPTION active booldata user 1 "data part"
package CYGPKG_MY_PACKAGE
component CYGPKG_DATA_OPTION active data inferred "abc def ghi"

Note that each line is a space-separated list where the Nth item of the list
has a fixed meaning. The 3rd item is always the active/inactive state, the 5th
item (where present) is always the value source, etc. Note, also, that values
containing spaces are surrounded by double quotes.

In this way we can import the dump into a spreadsheet, or pipe it through "cut"
to extract only those parameters of interest, or "sort" on the CDL macro name,
etc.

Do you have any interest in modifying your patch along these lines? Any other
comments?

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug 1001632] Patch for making it easy to diff ecos configurations

[bugzilla-daemon]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001632

Jonathan Larmour <jifl@ecoscentric.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jifl@ecoscentric.com

--- Comment #5 from Jonathan Larmour <jifl@ecoscentric.com> 2012-08-02 01:40:03 BST ---
I'm not averse to this addition (although it does definitely need to account
for value_source), but is it perhaps a little redundant? You can get something
quite diffable by exporting a minimal eCos config (a .ecm file) from each .ecc
file, and then diffing those two files. That's what I've done in the past and
it's always been sufficient...

If it is still thought necessary, I agree that John's suggested formatting
would be better, to make it more regular.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug 1001632] Patch for making it easy to diff ecos configurations

[bugzilla-daemon]

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001632

John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO
                 CC|                            |john@dallaway.org.uk
         AssignedTo|unassigned@bugs.ecos.source |john@dallaway.org.uk
                   |ware.org                    |
     Ever Confirmed|0                           |1

--- Comment #4 from John Dallaway <john@dallaway.org.uk> 2012-08-01 20:40:24 BST ---
Hi Martin

Thank you for your contribution. I like the idea of a dump command that emits 1
line per CDL item for use with diff and other tools.

I think the format of each line could be improved because:

a) The active/inactive state of a CDL item is distinct from its value and it
seems good to reinforce that distinction in the line format.

b) It can be important to know when the value _source_ (default/inferred/user)
has changed, even if the value has not changed.

My suggested line format, by example, is as follows:

component CYGPKG_MY_COMPONENT active bool default 1
option CYGSEM_MY_OPTION inactive
option CYGOPT_BOOL_OPTION active bool user 0
option CYGOPT_BOOLDATA_OPTION active booldata user 1 "data part"
package CYGPKG_MY_PACKAGE
component CYGPKG_DATA_OPTION active data inferred "abc def ghi"

Note that each line is a space-separated list where the Nth item of the list
has a fixed meaning. The 3rd item is always the active/inactive state, the 5th
item (where present) is always the value source, etc. Note, also, that values
containing spaces are surrounded by double quotes.

In this way we can import the dump into a spreadsheet, or pipe it through "cut"
to extract only those parameters of interest, or "sort" on the CDL macro name,
etc.

Do you have any interest in modifying your patch along these lines? Any other
comments?

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.