Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Combo packages proposal

It would be important, IMHO, to be able to specify a dependency to a particular build, ie, Ix, Mx
Can this be done now?
Being able to specify this dependency would help, I think.
Also, providing an 'official' repository for these projects sure would give the software update rounines more usage and from there testing, improving...

Jeff McAffer wrote:

I think we should be able to.  Some reasons people currently cannot:
- Eclipse does not make the elements of Eclipse available on a update site.
- Eclipse does not use version numbers in a way that supports update well (i.e., we do not increment the numbers)

Jeff



Mike Wilson/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx

02/12/2004 11:46 AM

Please respond to
eclipse-dev

To
eclipse-dev@xxxxxxxxxxx
cc

Subject
Re: [eclipse-dev] Combo packages proposal







Why can't this just be done via install/update?

McQ.




Jeff McAffer/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx
12/02/04 08:05
Please respond to
eclipse-dev


To
eclipse-dev@xxxxxxxxxxx
cc

Subject
Re: [eclipse-dev] Combo packages proposal







We have been battling with the packaging issue for years (literally).  For
every person that asks for the combo pack, there is some one complaining
that the SDK is too big.  For every person who wants WebTools, or VEP or,
... there are people who don't.  Given that we have some 8 platforms to
consider, each new packaging is quite a challenge to create, make
available and maintain.  We also have to consider the impact on our
mirrors.  Combo packs do not scale and they IMHO are fundamentally at odds
with the component model put forward by Eclipse (i.e., why should Eclipse
get to ship a huge wad when we tell everyone else to use components,
update sites, ...)

Don't get me wrong.  The problem you are encountering is real.  The
approach I would prefer to see is embracing the component model and make
it easy for people to a consistent set of the features/plugins they want.
For example, imagine a site where you pick the base Eclipse version (e.g.,
2.1.2, 3.0M6, ...), the platform(s) and the components you want (by name).
The site then picks the appropriate zips, jars, ... , combines them into
one zip and downloads it to you.  This sounds like an excellent
opportunity for someone with web service, web app, php, ... experience to
contribute to the Eclipse community in a real and tangible way.

Jeff



Miguel Griffa <mgriffa@xxxxxxxxxxxxx>
Sent by: eclipse-dev-admin@xxxxxxxxxxx
02/12/2004 12:36 PM

Please respond to
eclipse-dev


To
eclipse-dev@xxxxxxxxxxx
cc

Subject
Re: [eclipse-dev] Combo packages proposal








Please, oh God! please do so
I find it frustrating to have to download these subprojects separately
and have to read to see which version should I download for my eclipse
version.
I think  I'd be a great help to these projects if they are more
available for end users.

Sorry, for the comment not being a developer, I just think this would be
great.

Ed Burnette wrote:

>With tools such as GEF and EMF being used by more and more people and
projects, I propose that combination packages (which might be implemented
as nested features) that are bigger than the SDK be created and made
available for download. This will make it easier for users to identify,
download, and install the software they need in one step instead of many
steps. Ideally the schedule would be the same as the SDK.
>
>For example this combination would be helpful:
>
>    Platform SDK
>    Example plug-ins
>    FTP and WebDAV
>    GEF
>    EMF
>    XSD
>    VEP
>    WebTools (when available)
>
>Trying to match up version numbers for compatible features is a large and
growing problem, and combo packages would help fix that. Instead of 8
downloads, the user would just have one.
>
>--Ed
>_______________________________________________
>eclipse-dev mailing list
>eclipse-dev@xxxxxxxxxxx
>To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
>http://dev.eclipse.org/mailman/listinfo/eclipse-dev
>
>

_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
http://dev.eclipse.org/mailman/listinfo/eclipse-dev


_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://dev.eclipse.org/mailman/listinfo/eclipse-dev



Back to the top