Hello Sharlatan, That is understandable, but I guess you can already see how diverse these customs are between one ecosystem and another.
I was simply asking if these practices can either be documented clearly or made uniformly. Regards, Divya Ranjan On 23 November 2024 15:34:24 GMT, Sharlatan Hellseher <sharlata...@gmail.com> wrote: > >Hi Divya, > >Speaking from Python/Golang/Astro teams perspective. > >I see and use *-next where I need the latest package version but >updating inherited one would trigger a large amount of re-builds. It may >be swap on dedicated team branch when more packages start needing it. > >In Golang, there are breaking changes versions which are specified in >module path and reflected in Guix' package names e.g. >go-github-com-<owner>-<project>-v2 > >If updating package does not trigger more than 300-400 related packages >there is not need to introduce *-next variant and it's reasonable just to >update to the latest version. > >Hope it helps > >Live well! > >-- >Oleg Divya Ranjan, Mathematics, Philosophy and Libre Software
