On Wed, Aug 09, 2006 at 09:31:36AM -0500, Grant Edwards wrote:
> 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?
Im not sure its actually documented somewhere. It is something Bart
added a few years back. Im guessing eCosCentric use it internally to
keep customer specific packages seperate from there customer
independent packages.
> 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. ;)
At the time it was added, John commented that it required some work to
make configtool support this. So i was never added. To me it seems
like the configtool is unmaintained anyway. If it stays like this, i
would suggest it is dropped in the next official release. This is a
shame given that there has been some recent interest in bringing it up
to date with recent versions of xWidgets and make it build using
automake.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
