[Buildroot] [RFC] rename docker-containerd package to containerd?

[Arnout Vandecappelle]

 Hi Christian,

 Not much reaction to this RFC :-)

On 12/03/2021 22:00, Christian Stewart wrote:
> Hi all,
> 
> When introduced, the docker-containerd package was associated with
> Docker Engine.
> 
> Now, the project is independent and called simply "containerd."
> 
> https://github.com/containerd/containerd
> 
> Is it worthwhile / standard practice to rename the Buildroot package
> to "containerd"? The package is already independent from Docker.

 It's done occasionally, there's no real rule for it. Personally I don't like
renames too much, because it makes upgrading buildroot harder (though the legacy
handling usually covers it pretty well). It also makes backporting patches more
difficult, and also consulting history.

 If you look at Config.in.legacy ("git log -G '[Rr]enamed' Config.in.legacy"),
you'll see that for most renames there was a reason. For example, cegui06 was
renamed because it was no longer version 6. The rename of rcw -> qoriq-rcw was
contributed by someone from NXP (i.e., the chip vendor behind qoriq) so that
also carries a bit more clout.

 That said, feel free to do this rename if you think it improved things. Since
there's only a single package that depends on it, it shouldn't be too hard to do
the rename.

 Regards,
 Arnout

> 
> There would need to be mappings from the legacy Config.in entries.
> 
> Thanks & best regards,
> Christian Stewart
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>