Depend on a specific version of a library

[FWeinb]

Resolved

• http://docs.platformio.org/en/latest/projectconf/section_env_library.html#lib-deps

---

This is probably related to #410. To support reproducible builds and work on projects that depend on the same library but a different version it would be best to support a way of installing library with the Project and not as a global package of platformio. To get this working one has to define a version range in addition to the library in lib_install.

[ivankravets]

TODO: add new lib_deps field to platformio.ini with the next format:

lib_deps = 
    %LIB_NAME%@%semiver1%,%semiver2%,%semiverN%
    id=%LIB_ID%@%semiver1%,%semiver2%,%semiverN%
    https://github.com/author/project.git
    https://github.com/author/project.git@tag
    https://github.com/author/project.git@commit

For example,

lib_deps = 
    Json@^1.0.0
    id=64@>=1.0.0,<2.0.0,!=1.5.7
    https://github.com/gioblu/PJON.git
    https://github.com/gioblu/PJON.git@v2.0

@marvinroger, @FWeinb WDYT?

[ivankravets]

Currently all libs will be installed in http://docs.platformio.org/en/latest/projectconf.html#lib-dir. What I should do when 2 projects require the same libs with different lib_requires? Is it good idea to install required libraries directly to project's lib folder?

[marvinroger]

lib_requires should be spelled lib_require, as we currently have lib_use and lib_ignore without the leading s. So lib_install will be deprecated/removed? Otherwise It would sounds redundant.
And I would remove the commas, just Json: >=1.0.0 <2.0.0 !=1.5.7 as this is more common and standard.

Maybe you could store libs by library and version. I mean:

* Json
    * 1.0.0
        * src...
    * 2.0.0
        * src...

What's the benefit of storing the library in the project folder? I can't find any. But storing it globally avoids to download multiple copies of the same library (ArduinoJson for example will probably be used in multiple projects).

[marvinroger]

Plus, we would have to .gitignore the lib folder if we use Git. I'd stay on the global install.

[ivankravets]

lib_requires should be spelled lib_require, as we currently have lib_use and lib_ignore without the leading s. So lib_install will be deprecated/removed? Otherwise It would sounds redundant.
And I would remove the commas, just Json: >=1.0.0 <2.0.0 !=1.5.7 as this is more common and standard.

Done! #413 (comment)

Maybe you could store libs by library and version. I mean:

npm uses this scheme. Oh... How much work need to do with it. Yes, this scheme is the best from all views. Because project's lib was intended for private/specific libraries

[andig]

Please make sure to add ability for requiring dev versions as well (both for libraries and platforms ;)