This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
AW: Splitting the eCos repository
- From: "Neundorf, Alexander" <Alexander dot Neundorf at jenoptik dot com>
- To: Øyvind Harboe <oyvind dot harboe at zylin dot com>
- Cc: <ecos-discuss at ecos dot sourceware dot org>
- Date: Fri, 11 Aug 2006 16:53:47 +0200
- Subject: AW: [ECOS] Splitting the eCos repository
> Von: ecos-discuss-owner@ecos.sourceware.org
>
> How about splitting the eCos repository?
>
> - It would help to market the support for multiple repositories. I've
> seen a lot of messy maintainence due to the lack of this knowledge.
> - It would reduce the size of the eCos repository that 90% use.
>
> Something like:
>
> - eCos core. Up to and including architecture HAL's
> - eCos devboard. Contains all the HAL's for development boards.
> - eCos highlevel/net. All high level(many files) stuff like net,
> microwindows, etc. goes
> - eCos legacy.
>
> 1 eCos repository is too little, 10 is too many. :-)
>
> The user would then have to either use a development board HAL as-is
> or create his own eCos repository, probably duplicating & modifying an
> existing HAL.
I'd say not before configtool supports it.
But it would also make creating a public "experimental" repository possible (e.g. on sourceforge) for stuff which didn't make it yet into the main repository.
Alex
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss