|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.}
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.
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-09for 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 the end, I think there are other approaches than a respin that would help minimize (and in many case eliminate) the problem.
Back to the top