|Re: [cross-project-issues-dev] MPC not opening with space in install path - requesting respin|
Probably the worst case would be if the user's home folder name has spaces "C:\Users\john doe", but I suppose that in (almost?) all cases the user could choose to install to a location without spaces and in all cases the user can update MPC from a specific URL.
Given we are no longer in the business of providing update
releases, to me it's a slippery slope to me if we start respinning
releases to publish multiple releases. My knee jerk reaction is
to vote -1 on a respin.
Certainly the decision of whether we will do respins affects the
decision of whether http://download.eclipse.org/releases/2018-09
for the September release can be a simple repository because there
can/will never be updates versus whether it should be a composite
to accommodate arbitrary/possible respins.
In any case, the combination of "I install to a disk location
with spaces" (which is generally always a bad idea because
something is bound not to work properly because it's not been
tested) with "I actually use MPC" is probably relatively small,
but who knows.
Note that another possible solution to this problem for users who
create their installations with the Eclipse Installer is to add
the URL the MPC fix to the Oomph Product Catalog for all Photon
Product Versions. I tested this for installing the Committers
Photon Product Version. I can see in the log (below) that it's
loading your repos and in fact downloading the 1.7.1 versions of
MPC's bundles. Note that I would not be happy to add a repo URL
that composes so many other repos. E.g., you can see it's loading
a bunch of milestones and even nightly build repos. If we do add
a URL, it should probably be specifically
http://download.eclipse.org/mpc/releases/1.7.1 right? I tested
that as well,
Along a similar line of thinking,
http://download.eclipse.org/releases/photon is a composite and
http://download.eclipse.org/mpc/releases/1.7.1 could be added to
that composite. This would make check for updates work (I assume)
and it would ensure that the existing Oomph Product Catalog would
directly install the latest version of MPC during the initial
installation process. That would only leave the problem of
unzipped packages not including the fix, but a comment on the web
page where this is downloaded would somewhat help address that.
In the end, I think there are other approaches than a respin that
would help minimize (and in many case eliminate) the problem.
----- Eclipse Installer Log ----
On 30.06.2018 00:54, Carsten Reckord wrote:
Back to the top