You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We found a problem regarding the field version in the section provider of a core and the fusesoc cache folder.
When the value in the field version is changed from v1.0.4-rc0 to v1.0.4-rc1 for example, fusesoc doesn't notice this and the files are not updated in the cache folder. The only known workaround is to change the version in the core :some:core:1.0.4 => :some:core:1.0.5 which is not possible, because the core is used as a dependency of another core and an update of the version number of the core would cause a domino effect.
We have a single repo for all our cores and the cleanest solution to this problem would be if fusesoc checks also the version in the provider section.
We found a problem regarding the field
version
in the sectionprovider
of a core and the fusesoc cache folder.When the value in the field
version
is changed fromv1.0.4-rc0
tov1.0.4-rc1
for example, fusesoc doesn't notice this and the files are not updated in the cache folder. The only known workaround is to change the version in the core:some:core:1.0.4
=>:some:core:1.0.5
which is not possible, because the core is used as a dependency of another core and an update of the version number of the core would cause a domino effect.We have a single repo for all our cores and the cleanest solution to this problem would be if fusesoc checks also the version in the provider section.
I think this issue should be classified as a bug.
The text was updated successfully, but these errors were encountered: