Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Talk:Callisto Coordinated Update Sites"
m |
|||
Line 1: | Line 1: | ||
− | My comments ( | + | My comments (Kim Moir platform-releng) :-) |
(1)There is a problem with the url | (1)There is a problem with the url |
Revision as of 18:43, 3 February 2006
My comments (Kim Moir platform-releng) :-)
(1)There is a problem with the url http://update.eclipse.org/updates/callisto/
Currently, the platform team stores all its updates in this directory
http://update.eclipse.org/updates
and subdirectories such as these
http://update.eclipse.org/updates/3.0 http://update.eclipse.org/updates/3.1
So I don't know that this is the best url for Callisto
http://update.eclipse.org/updates/callisto/
given that we already have platform content in that directory we can't change the Apache alias for platform because this has been hardcoded in our feature.xmls the unix permissions on the directory mean that the platform team would need to retain ownership in order to continue update the content in the existing update sites.
(2)Providing Callisto as a single download comprising all 10 projects provides better exposure to the newer projects. By the same token, it also forces people to download stuff that they may not necessarily want or ever use, thus significantly increasing the strain on the distribution infrastructure. It is also rather overwhelming for a new eclipse user. My point is, perhaps there is a better way to educate users and provide choice while simultaneously exposing the full breadth of functionality available with Callisto.