Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mpc-dev] Remediation support and MPC target platforms

Though this is true, the conditions where this would work are rather specific, since the user would have to have added the MPC repo or the Kepler repo, and have originally installed MPC by himself since the MPC in EPP can't be updated individually.

I honestly think that we are bending over backward for a very unlikely use case, and updating the plan would be easier to do rather than keeping eternal backward compatibility.

On 2013-05-07, at 5:21 PM, Carsten Reckord wrote:

> 
> 
> Ian Skerrett <ian.skerrett@xxxxxxxxxxx> wrote:
> 
>> I am hoping Steffen and Benjamin might comment on any historical reason
>> for the backward compatibility requirements.  I would tend to think
>> that people using the Kepler version of MPC will be using it with
>> Kepler.  However, I might be missing a use case?
> 
> 
> Well, currently Helios/Indigo users will automatically profit from all the same new bugfixes and features through the automatic update check without us actively maintaining separate versions for those platforms.
> 
> That's really the only reason I could think of.
> 
> _______________________________________________
> mpc-dev mailing list
> mpc-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mpc-dev



Back to the top