Any idea when it will be released?
If I understood correctly the library manager (package manager) now also automatically deletes dependencies from .pio folder. Is this correct and can this feature be disabled?
Some how I am now experiencing that it is deleting (or re-installing) dependencies without changes to that specific dependency in the platformio.ini… also deleting any changes i had made and not yet pushed
I meant that I made “manual” changes to the lib in the .pio/libdeps folder and had not yet pushed those changes to the repository on github.
I know this isn’t the ideal situation but it seems the only way to develop changes to dependent private libraries. I’ve tried including private libraries as submodules of my main repository but that doesnt go well with the dependency finder as it does not download the dependencies of the library when building
I understand that .pio is temporary and only meant to include readonly clones of stable libraries …
But in our situations the (many) private libraries that we use are not stable yet, they are developed while we are developing projects that use them.
In the ideal world any library changes needed would first be made in a separate local clone of the library, tested there and then pushed to the repository so platformio can update them in the .pio of the main project. But given the amount of changes needed and only limited possibilities to test those changes on hardware outside of the main project, this will not work for us.
That is why we are making changes to libraries from within the .pio/libdeps folder
But then I would push those into the lib/ folder and edit them there, then they won’t be in the libdepsibs folder. The new core also has lib_deps = symlink://<some path> which will not make a local copy anymore but a symbolic link.
I tried including libraries as submodules of my main project, having them cloned in the /lib folder, but then the library dependency finder doesn’t process them correctly, and also downloads them in the .pio/libdeps folder or doesn;t include dependencies of that library in the .pio/libdeps
I would love to have a better solution for the way we are working now, but I can’t seem to find any that also still make the main project containing all needed dependencies so I can just clone the main project, “press build” and it will do everything needed and complete the full build from scratch
I think that actually without the library.json of lib1 it would work (deleting it).
I think this case is tricky – if the library.json wants the git version explicitly, but it also exist in lib/, what does it respect? The version in lib/ may not be the git version. On the other hand one could say if it was manually put in lib/ then we can always infer that that version is to be used.
How do I “… remove installed packages with PIO Core 6.0 and reinstall them with PIO Core 5.0…”? I am using macos, I uninstalled PlatformIO and VScode and deleted my .platformio directory. I reinstalled both, but no luck.