Specify older library version using SHA?

glynhudson · June 8, 2016, 12:33pm

As far as I gather if no specific version is mentioned in the library.json manifest file then the first 10 characters of the git SHA is used to specify the version. e.g. a lib can be installed with:

- platformio lib install 252 --version="e70c9d9f4e"

I would like to use a version of this library (JeelLib) from a few commits previous, is seems it’s not currently possible to specify and older version by installing the lib with previous SHA commit e.g.

- platformio lib install 252 --version="64bdc605dc"

This results in a platformio API error, am I missing something or has this feature not been implemented? Being able to specify exactly what version of a lib I want to use is very important for my project future replicability.

Very impressed with platformio btw, good job

ivankravets · June 8, 2016, 1:19pm

This is PlatformIO 3.0. See PlatformIO 3.0 Library Manager related issues.

I recommend to use temporary lib_install option for platformio.ini and remove these lines

github.com

openenergymonitor/emonpi/blob/master/.travis.yml#L36:L45


      
          language: python
          python:
          - '2.7'
          sudo: false
          cache:
            directories:
            - "~/.platformio"
          install:
          - pip install -U platformio
          
          script:
          - pio --version
          - platformio run -d firmware -e emonpi_deploy
          
          deploy:
            provider: releases
            skip_cleanup: true
            overwrite: true
            api_key:
              secure: OzNwxsQEVlSj2e4sOqKNYlNXqPqc5myL0nOBtY1FYD+sbxslHMixmlRASWuFMCjHdpFYQST2IuR3UMCPCjfPzMDVCVtsJ8VPd299fgDGzmEnL3P5Z8wCAv1CfHURcfXzFJDM7prevGx9cfz8uAiwIaNOhbTL7kL2GfSatV5PERzr2ytVh6WUj650Rd7bLKKhj8YHOzO9wOBoKDadYDFF99XYQbDDoHj9pAv+OPG76X0kWrdrq/0w26jh7JZaxrwhF/xD7maGaEjLOa/FcXbyZlVy/JIFjyrKp79swzVNSFNox/CbF7e6tzBf3NhZsoQyEchnCrgWw8IB7j/Ja7Ypetn6IG7C5rT/h46rWrZshbVdw7ZBUzhNJIUVLHFBy7hi2hxMw9Bn+oCt0UWLt8SnQnRfAbjw+z3XQ2/6MccUAINKGDqd4fm9M85sN6drpXySeJ/ZyRkdlUN0xsDpARI05mYLLlCutRzlSCkglbsKJr5XM7h7pXHLUQY5dfw9LrA788w25OBoO9U8vCKtoV8UCXWh6og/364CRl9Uih958f1t7kHIvfwLJjwSDFYVxUsyvSFyjfY+pIfuGEXtgIqMZ87nK3O1vAb9udbPErp0q5kJBeks9Df6wVsvjI7O++7YwiSuWlJBD0x45ZV9pxOFLnWb1hetHpPH5kFgBlTDqsY=
            file: "firmware/.pioenvs/emonpi_deploy/firmware.hex"
            on:
              repo: openenergymonitor/emonpi
              all_branches: true
              condition: $TRAVIS_TAG =~ ^[0-9]+\.[0-9]+\.[0-9]+$
          
          
          ## Setup auto depoly .hex on release tag
          # sudo gem install travis
          # cd into repo
          # $ travis setup releases
          # folow prompts..depoly section will be populated
          
          # http://blog.openenergymonitor.org/2016/06/auto-build-continuous-test-firmware/

What is more, you can specify direct path for the project directory. This line is equal to platformio run -d firmware

Thank you! Please follow us on Twitter.

glynhudson · June 8, 2016, 1:34pm

Wow, it looks like you have been busy improving lib management with 3.0.

Is 3.0 ready for testing? I’m currently running 2.9.4, do I need to update before I can use lib_install option? The docs don’t mention if lib version can be specified with lib_install? e.g.

lib_install = 1 --version="xx"

It’s a nice improvement to define libs and versions in platformio.ini. That way both the compiler and travis can use the same definitions

Nice, thanks, I’ve removed the cd command and replaced with above

Done, I’ve got a blog post ready to post up on our blog. I’m sure lots of folk on our community will be interested in using platformio. After fighting with Arduino IDE and lib versions for the past 6 years platformio feels like a step change

ivankravets · June 8, 2016, 1:52pm

Here is the separate branch https://github.com/platformio/platformio/tree/feature/platformio-30. The all source code that relates to development platforms has been moved to separate repositories. This is issue #479
"platform.json" manifest for development platform · Issue #479 · platformio/platformio-core · GitHub

The library manager has not been refactored yet. I’ve just invited you to PlatformIO Club/Slack Team. I’ll post here about further beta builds of PlatformIO 3.0.

It looks that PlatformIO Library Registry doesn’t contain that version.

glynhudson · June 8, 2016, 7:33pm

Going forward will platformio library register containing SHA versioning for each commit to libraries? Does the library not contain the SHA I am after since this is an older commit made before your library crawler was active on this library repo.

ivankravets · June 10, 2016, 11:16am

You are right. Currently, the registry contains only the versions since the library was registered. You will be able to use VCS with specific branch/tag/commit in PlatformIO 3.0.

See example how does PlatformIO 3.0 allow to use verion of development platform:

The same functionality will be implemented for Library Manager.