Hi there,
I’m currently working on the next revision of the Luos library.
I would like to rename this lib from Luos
to Luos_engine
or something and keep the history.
Is it possible?
Hi there,
I’m currently working on the next revision of the Luos library.
I would like to rename this lib from Luos
to Luos_engine
or something and keep the history.
Is it possible?
I’m not sure if the PlatformIO is redirect-capable if we rename the library.
CC @ivankravets any ideas (if you’re available)?
Hi,
The package has been renamed. All your customers who previously used Luos
name are affected. Please ask them to update their project dependencies.
Whaou!
That was fast!
To be honest, I wasn’t ready. We have to update all our documentation and examples first.
As I understand there is no redirections from luos/Luos
to luos/Luos_engine
?
Yes, no redirection. Should we revert back the changes?
Yes please @ivankravets
Now I know how it’s working, I will let you know when we are ready
Sorry about that.
@ivankravets I was wondering, instead of renaming the lib could it be possible to duplicate it with a new name and keep both of them?
We could add a warning deprecated message at compile time for the old ones and this could allow our users to make a smooth transition.
I don’t want you to make it right now, I just want to know if this is possible.