[ECOS] Splitting ecos.db?

[ECOS] Splitting ecos.db?

[Stanislav Meduna]

Hi,

is there any possibility / script / work in progress to synthetise
the ecos.db file from several sources?

We are developing for several customers who are getting sources,
but they generally should not see what else we are working on.
It is no problem to only export part of the source tree,
but the ecos.db makes a problem here.

Is there actually any information in "package" entries
that can't be synthetised from the .cdl files in the tree?
Redundant information is often a recipe for problems...

And is there any special reason to keep "target" entries
together with the package information?

Is there at least a way to specify an ecos.db file to be
used by the ecosconfig / configtool?

Thanks
-- 
                                   Stano

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] Splitting ecos.db?

[Gary Thomas]

On 06/06/2011 09:09 AM, Stanislav Meduna wrote:
> Hi,
>
> is there any possibility / script / work in progress to synthetise
> the ecos.db file from several sources?
>
> We are developing for several customers who are getting sources,
> but they generally should not see what else we are working on.
> It is no problem to only export part of the source tree,
> but the ecos.db makes a problem here.
>
> Is there actually any information in "package" entries
> that can't be synthetised from the .cdl files in the tree?
> Redundant information is often a recipe for problems...
>
> And is there any special reason to keep "target" entries
> together with the package information?
>
> Is there at least a way to specify an ecos.db file to be
> used by the ecosconfig / configtool?

Look (far) back in the list archives - I'm sure that Bart mentioned
something about this many years ago.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] Splitting ecos.db?

[Stanislav Meduna]

On 06.06.2011 17:12, Gary Thomas wrote:

>> is there any possibility / script / work in progress to synthetise
>> the ecos.db file from several sources?

> Look (far) back in the list archives - I'm sure that Bart mentioned
> something about this many years ago.

Thanks for the pointer, the relevant mail is

http://ecos.sourceware.org/ml/ecos-patches/2003-03/msg00195.html

Looks this can be what we need, I'll try it.

Thanks
-- 
                                       Stano

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] Re: Splitting ecos.db?

[Grant Edwards]

On 2011-06-06, Stanislav Meduna <stano@meduna.org> wrote:

> is there any possibility / script / work in progress to synthetise
> the ecos.db file from several sources?

You can specify as many repositories as you want using normal "PATH"
semantics for the ECOS_REPSOTORY environment variable.  Each
repository has it's own ecos.db file.  They're searched in the order
in which they appear in ECOS_REPSOTORY.

> We are developing for several customers who are getting sources, but
> they generally should not see what else we are working on. It is no
> problem to only export part of the source tree, but the ecos.db makes
> a problem here.

Will splitting up repositories solve your problem.  For example you
can have one "standard" repsotory containing the "standard" stuff from
the CVS tree.  Then you can have another repsotory for "private" stuff,
and a third for "modified standard" stuff that overrides the
"standard" stuff (by virtue of appearing before the "standard"
repository in the ECOS_REPOSITORY path).

> Is there actually any information in "package" entries that can't be
> synthetised from the .cdl files in the tree? Redundant information is
> often a recipe for problems...

I think so, but don't quote me.

> And is there any special reason to keep "target" entries together
> with the package information?
>
> Is there at least a way to specify an ecos.db file to be used by the
> ecosconfig / configtool?

-- 
Grant Edwards               grant.b.edwards        Yow! I've got an IDEA!!
                                  at               Why don't I STARE at you
                              gmail.com            so HARD, you forget your
                                                   SOCIAL SECURITY NUMBER!!


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] Re: Splitting ecos.db?

[Stanislav Meduna]

On 06.06.2011 17:26, Grant Edwards wrote:

> You can specify as many repositories as you want using normal "PATH"
> semantics for the ECOS_REPSOTORY environment variable.  Each
> repository has it's own ecos.db file.  They're searched in the order
> in which they appear in ECOS_REPSOTORY.

Note: this does _not_ work with configtool on cygwin - something
there converts the paths to windoze format and then of course
the colons in 'C:\...' break everything.

Anyone knows of a patched configtool version that works? Having
to abandon the configtool is a PITA and switching to Linux
is unfortunately not an option right now :(

Regards
-- 
                                   Stano

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] Re: Splitting ecos.db?

[Stanislav Meduna]

On 17.06.2011 20:09, Stanislav Meduna wrote:

> Anyone knows of a patched configtool version that works? Having
> to abandon the configtool is a PITA and switching to Linux
> is unfortunately not an option right now :(

OK, the one from http://www.ecoscentric.com/devzone/configtool.shtml
seems to work. Any reason why the environment installed via
http://ecos.sourceware.org/getstart.html does not include it?

-- 
                                            Stano

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss