Open rahulghangas opened 4 years ago
@rahulghangas one con that I can think of is the maintenance of projects/programs related to that package. Updating the global package would make all your projects use the updated version. Some packages might break compatibility with further dependencies.
I do agree that updates can be a hindrance, but I'm thinking that this is a limitation only because of the current state of the project. Once Chapel starts doing more stable releases, this should become less of an issue.
Food for thought: Once we have more stable releases, maybe Chapel can then start following the SemVer philosophy a little more seriously, with patches being backwards compatible to make sure you don't break anyone's code.
Is it more possible in the global scope we would have a package conflict? For example, the names of sources conflict between different packages.
As a user, it would be nice if I could install mason packages globally and use them in my day to day programs. This issue is to discuss the pros and cons of this.