![]() ![]() Using a fragment of my own spell-check, it looked like this: // from spell-check Atom (one of my favorite editors that was sadly killed) had the idea of services where a package could provide a service (that had a version) and other packages could “consume” them. For example, Minetest modules can check for the presence of other modules and then hook up to them. The above example doesn't handle optional dependencies. ![]() “Something.Else” version 1.0.0 becomes bakfu.nuget:Something.Else?version=1.0.0. In the above example, if a module doesn't have a provides element, then we could assume that it is just the identity version. Using MfGames.Nitride?version=0.15.1 as an example, here is a fragment of what that could look like: When working with Bakfu, this is almost identical to the package identifier but without the bakfu:version and instead a range of values that are acceptable. I want to work out my ideas, maybe have a few conversations, and then start to move to more technical concepts.įor most systems, dependencies are very simple: this package requires these packages in this range. This is going to be a series of posts, but I have no idea of how fast I'll be writing them out. Without dependencies, packages would be forced to contain common logic that other packages share, and that code may become stale or not updated as frequently introducing potential bugs. While packages can be self-contained, usually they have dependencies with other packages or even frameworks to avoid duplicating code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |