ibilon
ibilon
Related to #161
Not sure how easy it'd be to migrate from a file to a directory. For the config I think we should have a single json file (`~/.haxelibconfig`?), and a single...
Could go for a simpler "one key-value pair per line" format, but I guess that depends on how much config values you need to get, if the parsing is more...
Thanks, I updated my suggestion with it, and move those into Server instead of HaxelibProvider, which makes more sense. Also most data structure from here https://github.com/HaxeFoundation/haxelib/blob/master/src/tools/haxelib/Data.hx could stay the same,...
https://github.com/openfl/hxpm/tree/haxelib/ It's a prototype of the API I linked in my first message, it has a cli completely decoupled from the logic code, it's multilingual and can easily be linked...
Cool thanks. There's a couple of things that didn't quite work the way I envisioned, the implicit save with setter actually make things confusing and more complex, the use of...
Does it work if you simply remove that line from the build.xml?
While important, just checking if a semver is in a "semver set" is not enough, we need to be able to specify a set in haxelib.json, and something a lot...
If think we can, in #265 there was two possibility but they are similar to what's discussed here: should an upgrade disable dev or just mention it, while install/local should...
clearlibs seems to remove anything but the latest version, while `prune` should keep the set version and any version specified in another lib. Some linux package manager have an `autoremove`...