classPaths in haxelib json about haxelib HOT 9 CLOSED

Good idea, although I doubt one really needs multiple class paths within the same haxelib. The compiler might actually not expect more than one classpath per lib returned by haxelib. So having just one optional custom classpath is what we could do.

from haxelib.

I also think a singular "subdir" value would be sufficient. Note that the haxelib git command already allows specifying a sub-directory while installing a library (haxelib git name path subdir).

from haxelib.

I was thinking something different than only a sub directory.

if it was only a subdir, while we could get the haxelib out of the source folder, we would still mix sources with the other files that are to be part of the lib (run.n, other files...).
So this is different than the git command but this feature could make the git subdir argument redundant (making life easier for users).

Maybe a "src" value ?

from haxelib.

I like this a lot. But we need to finalize the haxelib.json file format soon, right now it's really seeming unstable, which isn't good for a final relase

from haxelib.

Do you mean unstable as in "broken" or unstable as in "it's changing"? The change discussed in this issue wouldn't break backward compatibility, so I'm personally not too worried about it.

It would be good to finalise a specification though, so the work you've done in the other thread looks good.

from haxelib.

Unstable as in changing.

If the haxelib format were under semantic versioning, we'd be incrementing the minor counter a lot. Definitely better than major changes, still.. leaves a little bit of a bad taste in my mouth. This improvement it worth it though, for sure.

from haxelib.

Another note:

"haxelib install" and "haxelib local" currently have a functionality not too different to what we're proposing: they search the zip for the relevant "haxelib.json" file, and then unpack from that directory downwards. (See https://github.com/HaxeFoundation/haxelib/blob/master/src/tools/haxelib/Main.hx#L577)

I think I still prefer the implementation suggested in this issue, as it would let you bundle documentation, examples, test cases or supporting files and not have them pollute the class path.

from haxelib.

Added in ad284d9

from haxelib.

Also need to add it to manual.

from haxelib.