[ECOS] About .ecm files

[surya prakash]

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.


> I had to
> ship the customer the .ecc also..
>
> twas a while ago and I've no idea if I can reproduce it at the moment
> :-)
>
> Regards,
>         Dave.
>
>  In this context, they are supplied to give you a "potted"
> > configuration to build redboot for various startups.
>
> >
> > They're not a required part of the port as such - you can just set the
> > options yourself in the configuration - but they are included so that other
> > people can build redboot without having to know the details of exactly what
> > options to set or packages to add.
> >
> > 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
> --
>       David Airlie, Software Engineer, Parthus Technologies plc.,
>        Mary Rosse Centre, National Tech Park, Limerick, Ireland.
>    t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com