On Wed, Jul 24, 2019 at 03:30:57PM -0400, Andrew F. Davis wrote: > On 7/24/19 3:14 PM, Denys Dmytriyenko wrote: > > On Fri, Jul 19, 2019 at 05:06:19PM -0400, Andrew F. Davis wrote: > >> No one depends on this and it does not really get built, > >> remove this from PROVIDES. > > > > Bah, such a nice commit message. :) > > > > Seriously though, it is there for backward compatibility. That was the name > > of this package few years ago. Sure, "it does not get built", but claiming > > that "no one depends on this" is really a guess. There might be old recipes > > out there depending on this package by its old name... > > > > Anyway, I don't mind dropping this backward compatibility, since it's been > > several years already, but I would like to see a better commit message. > > How does backwards compat work with Yocto? Are you saying for out of > tree recipes? If so I'll change the wording to "No one *in-tree* depends > on this".
Yes, out-of-tree. Yocto Project embraces layered structure. There are tons of layers with interdependencies. There could be outdated layers (potentially customers) that use the old name. In order to drop backward compatibility, we need to provide a clear message. -- Denys -- _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
