Publishing CNL 1.x libraries to platformio about cnl

[henrygab]

@johnmcfarlane , thanks for the quick response, and pointer to the prior issue. I don't know why it didn't appear in my search (I did search issues first!). As for fork not appearing, that's because the library doesn't appear to be registered with PlatformIO. Instead, their solution is to include the library by specifying the git repo and tag directly, which PlatformIO supports:

lib_deps = https://github.com/maxgerhardt/cnl.git#v1.1.7-pio

Unfortunately, this means people searching for CNL with PlatformIO won't find that it's available for use, since only registered libraries can be searched.

Still... I greatly appreciate your responsiveness, and helping unblock me. 👍

[johnmcfarlane]

Hi Henry. Thanks for getting in touch and I'm glad to hear that you found CNL useful.

Addition of a PlatformIO manifest file was requested in #805. I was keen to explore a non-intrusive solution for reasons given there. This resulted in platformio/platformio-core/issues/3887 which remains open and CNL was forked as you suggest. I'm not sure why that fork doesn't show up in your search or how actively it is maintained, but if you wanted to publish your own fork, you'd be more than welcome.

I'm still hesitant to add orthogonal package system files to the upstream for the same reasons given before. Perhaps you could weigh in on the issues mentioned here which seem to prevent seamless use of packages in PlatformIO.

[ivankravets]

Hi @johnmcfarlane,

Founder of PlatformIO here. There is no requirement to add library.json to the source code repository. You can copy a source code of v1.1.2 to some folder on your local machine, add library.json, and publish to the PlatformIO Registry. You will need to repeat this step on each release.