[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] CDT4.0RC3 - why only available as update sitefrom download page?
|
Beth -- Thanks for responding. I missed the earlier posts to cdt-dev
when I looked in the archives, sorry.
Is summary this change in releasing builds was made to conserve
disk space and bandwidth at eclipse.org. (looking at Doug's post).
Unfortunately collapsing every component into an update site has
made my workflow harder. Is there a possibility to change
the release process? Or to get some help with my workflow?
I can see that an update site is useful, and that individual features
can be installed via the update manager. Having a local cache of the
update site is basically an optimization for using update manager.
In my case I need to download individual components of CDT (at least
the CDT Runtime and SDK features) in an automated way without any
human interaction or running a GUI such as update manager.
Unfortunately going from an update site to an eclipse hierarchy of
features/plugins is a bit tricky. For example a feature in an update
site is a jar file, while it must be a directory in an eclipse
hierarchy.
It's also inconvenient to parse the feature.xml to get the required
plugins for that feature from a script (shell, make, or ant).
My concern is that such a script would be brittle and complex.
It certainly was a pain to perform the extraction and conversion
manually.
My preference is to add back some of the individual components to the
build.
Perhaps not every variant as before, at least more than all in one.
For example three components; Runtime, SDK and Extras might be okay.
Collapsing all platform architectures would be acceptable, if necessary.
Thanks for reading this far and for any help.
Robert.
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Beth Tibbitts
> Sent: Thursday, June 14, 2007 3:04 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] CDT4.0RC3 - why only available as
> update sitefrom download page?
>
> Doug appended here on that change a while back.
> Discussion is here on this thread:
> http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg09964.html
> Summary is here:
> http://cdtdoug.blogspot.com/2007/06/new-way-to-get-your-cdt.html
> I think he has a script that can extract what you need.
>
> ...Beth
>
> Beth Tibbitts (859) 243-4981 (TL 545-4981) High
> Productivity Tools / Parallel Tools http://eclipse.org/ptp
> IBM T.J.Watson Research Center Mailing Address: IBM Corp.,
> 455 Park Place, Lexington, KY 40511
>
>
>
>
> "Robert O'Brien"
>
> <Robert.OBrien@ac
>
> cess-company.com>
> To
> Sent by: <cdt-dev@xxxxxxxxxxx>
>
> cdt-dev-bounces@e
> cc
> clipse.org
>
>
> Subject
> [cdt-dev] CDT4.0RC3 -
> why only
> 06/14/2007 05:48 available as update
> site from
> PM download page?
>
>
>
>
>
> Please respond to
>
> "CDT General
>
> developers list."
>
> <cdt-dev@eclipse.
>
> org>
>
>
>
>
>
>
>
>
>
> For the recent RC3 build of CDT4.0 available from the
> download page at
> <http://download.eclipse.org/tools/cdt/releases/europa/dist/4.0.0RC3/>
> the build is only available as an update site with all CDT components.
>
> >From the main CDT page at <www.eclipse.org/cdt>:
>
> "CDT 4.0 RC3 is the second last release
> candidate for CDT 4.0.
> The final release candidate will be on June 22. Starting with
> this build, we will now only produce an update site with all
> features that are releasing with CDT 4."
>
> Why will the post RC2 builds only be available as an update
> site with everything?
> Is it possible to continue to make individual component
> builds available for download as with RC2 and earlier?
>
> I want to get just the CDT Runtime (for linux/x86 in
> particular) and package it for use in our company.
> Previously this was easy since there was a single download to use.
>
> With the merged update site form, I need to manually extract
> just the runtime bits which means I need to know exactly
> which feature and plugins to extract. Seems fragile if
> anything changes (e.g a new plugin is added or a name is changed).
>
> Additionally the feature is packaged as a jar for use as an
> update site, which won't work for a direct install into the
> features directory.
> So the feature jar needs to be extracted and properly renamed.
>
> My concern is that this is additional work for me (either manual or
> scripted) which makes me decide what contents define the CDT
> runtime feature instead of having that feature define its content.
>
> Any possibility of getting individual downloads again?
>
> Thanks,
>
> Robert.
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
