This is the mail archive of the ecos-bugs@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Issue 57324] .ecm files can't represent removed packages


http://bugzilla.ecoscentric.com/show_bug.cgi?id=57324


Bart Veer <bartv@ecoscentric.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE




--- Comment #3 from Bart Veer <bartv@ecoscentric.com>  2009-01-08 17:34:48 ---
This is not strictly true. The .ecm file generated at the end of these steps is
an accurate representation of the final configuration, and can be used to
rebuild that configuration exactly. However it does not hold any historical
information about the steps taken to produce that configuration. For that
matter, neither do .ecc files.

Note that the .ecm file still lists the "default" template, even though that is
no longer strictly accurate because the packages have been changed. However
that entry in the savefile is not used when recreating the configuration.
Instead the .ecm file lists the full set of packages, so there is no ambiguity.

What I think this bug report is asking for is a way of creating a configuration
as a series of simple steps, encoded in a small editable text file. For the
example provided a simple shell script suffices:

  #! /bin/sh
  ecosconfig new linux default
  ecosconfig remove CYGPKG_LIBC_SIGNALS
  ecosconfig add CYGPKG_POSIX

But that only works at a coarse grain, there is no supported easy way of
manipulating configuration options other than CYGPKG_INFRA_DEBUG. A more
general solution requires an implementation of CDL scripting, e.g.:

  #! ecosconfig cdlsh
  cdl_config new linux default
  cdl_config remove CYGPKG_LIBC_SIGNALS
  cdl_config add CYGPKG_POSIX
  cdl_set CYGPKG_INFRA_DEBUG 1
  cdl_set CYGDBG_USE_TRACING 1
  cdl_config save

That would give the functionality requested. It does not affect .ecm's which
would remain just a compact version of an eCos configuration save file. CDL
scripting is handled by a separate bugzilla issue so I am marking this as a
duplicate.



*** This issue has been marked as a duplicate of issue 57932 ***


-- 
Configure issuemail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]