Home » Developing U++ » U++ Developers corner » [Proposition] Simply source package manager for Upp
Re: [Proposition] Simply source package manager for Upp [message #54602 is a reply to message #54249] |
Wed, 19 August 2020 12:38  |
 |
mirek
Messages: 14267 Registered: November 2005
|
Ultimate Member |
|
|
Some thoughts:
- the "remote unit" should be nest. It is more general, often the code will comprise of more packages anyway.
- Package names should be unique in "uppiverse". Here I was considering that maybe we should introduce some UUID to resolve name clashes, in the end I have found that impractical
- I think the whole system should work by defining a special file, e.g. "remote" or "uppiverse" in the nest root which would contain references to other repositories. When loading main package, if package is missing, it would by automatically resolved by following these links. Repo would be downloaded into some "uppiverse" folder of nests and all nests of "uppiverse" would be automatically added at the end of assembly.
- Also, this establishes "distributed" network of packages, as crawling through these files should identify all nests/packages available, so some sort of "package manager" service would be possible (probably something like "add uppiverse package").
- One problem I see is that git does not provide functions to read individual files / folder from remote repo without cloning it. I think that this could be solved by limiting repo to github, where there is AFAIK API to get this info. We need this to list info about library and to get list of packages...
Mirek
|
|
|
Goto Forum:
Current Time: Tue Aug 26 14:34:31 CEST 2025
Total time taken to generate the page: 0.05311 seconds
|