[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [orbit-dev] pre-built libraries
|
Sounds cool.
Looks like we've been thinking a lot about versioning
the already-built bundles on some download site, while
the answer was right at hand (gee we should use a version
control system!)
CVS + mapfiles seems to do just the right thing.
FYI, I also commented on David's proposal on
http://wiki.eclipse.org/index.php/Promotion%2C_Release%2C_and_Retention_
Policies
in case you don't have Wiki Watch enabled, and putting
the pre-built stuff into CVS seems to solve what I've
been thinking about.
Cheers,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
> -----Original Message-----
> From: orbit-dev-bounces@xxxxxxxxxxx
> [mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of DJ Houghton
> Sent: Thursday, February 01, 2007 10:26 PM
> To: orbit-dev@xxxxxxxxxxx
> Subject: [orbit-dev] pre-built libraries
>
>
> As outlined in
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=170088 and
> talked about on this list before, we need to determine how pre-built
> libraries live in the Orbit world.
>
> I propose we do the following: (I will use ICU 3.4.5 as an example)
> - create the com.ibm.icu project in the repository
> - create a v3_4_5 branch
> - put the JAR in the branch
> - add a GET entry to the map file (as per
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=171869)
> - update the features, etc.
>
> David, does this sound ok or will this horribly break the
> build? (once the
> Get fetch factory is released into the builder, of course)
>
> Any other comments/objections from anyone else?
>
>
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
>
