Re: [ECOS] About .ecm files

[Jonathan Larmour <jlarmour at redhat dot com>]

Gary Thomas wrote:
> 
> On Mon, 2001-12-10 at 06:06, surya prakash wrote:
> > Dave Airlie wrote:
> >
> > >
> > > minus any package additions removal... which has bitten me a couple of
> > > times...
> > >
> > > not sure if still applies.. but I used to make a .ecc file with packages
> > > from the default system removed, and the .ecm would reflect it but
> > > importing said .ecm file would never change the packages ...
> >
> > I am sure that when we add a new target to ecos.db and build the configuration,
> > these changes are NOT reflected in .ecm files. Only the .ecc file is being
> > generated accordingly.
> >
> 
> The .ecm files contain "minimal configuration".  This means only the
> information which is required to recreate a given configuration.  The
> ".ecc" files (generated as part of creating a configuration) contain the
> complete set of configuration information.
> 
> One way to think about this is that the .ecm file has only the "actions"
> specified by a user to create a configuration.  The .ecc file contains
> the whole of the configuration.
> 
> For a given package configuration database (ecos.db) and templates, a
> .ecm file is sufficient to recreate any .ecc file, but much smaller
> (orders of magnitude).

I think Dave's point was that this doesn't apply to packages you *remove*
from the given configuration. You can only add to packages in a .ecm file.
I'll open a low pri bug about it.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine