Gee, I am super late to the thread, after starting it well over a year ago. Somehow I missed these replies.
I thing the answer (for me) is twofold. For quick prototype projects, I would prefer the "shifting sands" approach and keep my local MP repository up-to-date. With just one computer, I think there is no issue -- I keep my own ports as normal in the MP directory structure, and when I pull new MP updates, no worries (unless an update adds a file / folder with the same name as one of my custom projects). But alas, I work from multiple machines in different cities and different OSes. Probably making a custom "fork" for myself would be best, said fork would conceptually track constant MP updates and include my own changes. This way I can pull the whole shebang onto any computer of the moment.
But for a long-term project / product, I agree it is best to freeze your MP version. That could be simply a one-time clone of the MP repo in your project's directory with the .git folder removed so it won't be recognized as a submodule. Or alternatively make it a real submodule with a fixed commit hash.
I've been lucky so far that my projects haven't been impacted by a MP update. Quite the opposite ... there have been a couple of cases where getting the update helped me because of new features (I don't remember the exact details, but it was related to me trying to re-use a few classes from desktop C Python in MP as well).
I thing the answer (for me) is twofold. For quick prototype projects, I would prefer the "shifting sands" approach and keep my local MP repository up-to-date. With just one computer, I think there is no issue -- I keep my own ports as normal in the MP directory structure, and when I pull new MP updates, no worries (unless an update adds a file / folder with the same name as one of my custom projects). But alas, I work from multiple machines in different cities and different OSes. Probably making a custom "fork" for myself would be best, said fork would conceptually track constant MP updates and include my own changes. This way I can pull the whole shebang onto any computer of the moment.
But for a long-term project / product, I agree it is best to freeze your MP version. That could be simply a one-time clone of the MP repo in your project's directory with the .git folder removed so it won't be recognized as a submodule. Or alternatively make it a real submodule with a fixed commit hash.
I've been lucky so far that my projects haven't been impacted by a MP update. Quite the opposite ... there have been a couple of cases where getting the update helped me because of new features (I don't remember the exact details, but it was related to me trying to re-use a few classes from desktop C Python in MP as well).
Statistics: Posted by thestumbler — Fri Aug 11, 2023 7:55 pm