Replies: 4 comments
-
I think having a package "FsLab version 2" that is not backwards compatible (and contains stuff that is actually useful today) would be amazing. It is definitely reasonable for existing users of FsLab to pin their package version to "1.*" and not expect it to be updated (because it contains packages that themselves have not been updated in a long time). If "FsLab v2" also worked directly in .NET Interactive notebooks (with all the necessary visualizers installed), that would be very nice. |
Beta Was this translation helpful? Give feedback.
-
Yes totally reasonable to expect users to pin, and indeed best to allow yourself as many non-compat major version upgrades as you like in the future as well. |
Beta Was this translation helpful? Give feedback.
-
Okay awesome! Can one of you add me as owner of the nuget package so that's already taken care of once i get around to work on this? |
Beta Was this translation helpful? Give feedback.
-
@kMutagene Added, pending your approval! |
Beta Was this translation helpful? Give feedback.
-
I have thought a lot about integrating the fslab stack more tightly recently.
The next logical step for that would be composite packages offering e.g.
One roadblock for such a package is that there is already an existing fslab package on nuget. It was last updated 2018, but there still seem to be people that use it today
Would it be acceptable to expect those users to pin their versions and use that namespace for the composite package?
Comparable ecosystems such as scipy or tidyverse can both be installed via their respective names:
install.packages("tidyverse")
And i think having that for F#/.NET would be a great thing
As original owners of that package, what are your thoughts on this @dsyme @tpetricek ?
Beta Was this translation helpful? Give feedback.
All reactions