This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Issue 57324] .ecm files can't represent removed packages
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Thu, 8 Jan 2009 17:54:39 +0000
- Subject: [Issue 57324] .ecm files can't represent removed packages
- References: <bug-57324-13@http.bugzilla.ecoscentric.com/>
http://bugzilla.ecoscentric.com/show_bug.cgi?id=57324
Jonathan Larmour <jifl@ecoscentric.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|DUPLICATE |
--- Comment #4 from Jonathan Larmour <jifl@ecoscentric.com> 2009-01-08 17:54:38 ---
I think you are slightly misinterpreting the bug. Whether it was your original
intention at the dawn of time or not, the current intended use case for a .ecm
file is to reproduce the .ecc file from which it was based. Otherwise it cannot
be considered to be a minimal eCos configuration save file - it is lossy
compression! As such, it should be possible to start from the hardware and
package template listed in the .ecm file, and then import the minimal
configuration file, and obtain the original .ecc file. That does not happen. I
am not concerned with step-by-step history, merely the ability to reproduce the
original configuration.
If you are satisfied that the information (complete list of packages) is in the
.ecm file, then the import process should be acting on it - perhaps with a
command-line switch if you like.
If you think that CDL scripting is the basis of a correct solution to that
problem, then such a script needs to be generated by the export process, and
this bug should be used to track that requirement. Maybe .ecm files could even
be obsoleted and be replaced by a script. BTW, this bug would then have a
dependency on bug 57932, it does not duplicate it - see the "Depends on"
bugzilla field.
--
Configure issuemail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.