Is this a friendly or hostile fork? What are the core differences? Will the old one still be maintained and updated independently, or has it slowed down into obsoleteness? Having many similar versions of essentially the same code in Debian is confusing. However I think it is sometimes unavoidable. /Simon Arthur Diniz <arthurbdiniz@gmail.com> writes: > The new upstream is at https://github.com/yaml/go-yaml > > The reason why I decided to create it as a new package is that the *GO_PATH* > also changed from *gopkg.in/yaml.v3 <http://gopkg.in/yaml.v3>* to > *go.yaml.in/yaml/v3 > <http://go.yaml.in/yaml/v3>* and the same for v2 meaning that by creating a > new package we would have the name following the go-team standards. > > It's possible to create a symlink to maintain compatibility but still the > source and binary names would still be the old one. > > I'm open to dropping this ITP and working on updating the existing deps to > point to the new upstream but first I just want to know what are the best > practices here. > > Anyone else have any feedback on this? > > > On Fri, 15 Aug 2025 at 00:14, Mathias Gibbens <gibmat@debian.org> wrote: > >> This is going to be super confusing with the existing golang-gopkg- >> yaml.v3/golang-yaml.v2 packages. Would it make more sense to update >> those existing packages to point to the maintained forks? >> >> Mathias >>
Attachment:
signature.asc
Description: PGP signature