In gmane.os.ecos.general, you wrote:
>> It sure would be a lot easier to manage if the HAL was separate
>> from the main eCos tree. Have a huge tree of "off the shelf"
>> stuff with one modified file and one buried directory of
>> "custom" stuff is a real PITA to manage in a production
>> environment.
>
> ecosconfig understands ECOS_REPOSITORY being a list of directories.
> So you could have a repository of your own which just contains your
> HAL.
Cool. How did I not know that?
That would solve the problem very nicely: one "stock"
repository and one "custom" one containing HALs and whatever
other packages are too ugly (or just not generally useful
enough) to make it into the standard source tree.
> The configtool however does not understand the list thing.
> However, since you are talking about build scripts, i doubt
> that matters for you.
Hmm.
It would matter to me personally, but I think in the past there
have been customers who used the configtool to customize the
product's firmware. It sure would be easier to maintain if the
"custom" stuff was in a separate repository. I think it would
be worth giving up the configtool -- especially since it's
somebody else that doing the giving up. ;)
Right now when we decide to sync our eCos repository with the
"official" one, there always seems to be glitches.
--
Grant Edwards grante Yow! .. bleakness....
at desolation.... plastic
visi.com forks...
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
