On Tue, 9 Feb 2016 11:00:07 +0300, Andrew Savchenko wrote: > > > The idea is that users should ping developers with appropriate bug > > > reports. > > > > Instead, they ask in here or on the forums. Shouldn't the devs see > > such messages anyway and already be aware of the need to update the > > ebuild? > > They see them, but only when they build packages, e.g. when making > version bump. Eclass may become deprecated after last update of a > package, in such case devs may not see such warning because they > have no need to rebuild the package.
It still seems an awfully noisy and inefficient way of doing things. Can't the developer deprecating the eclass parse the tree for ebuilds still using it an d ping the developers, this sort of QA stuff should be automated , not rely on users seeing the messages and reporting rather than ignoring them. Anyway, the eclass has only been deprecated, the ebuild devs should be aware of this long before it is obsoleted. -- Neil Bothwick "There are no stupid questions, just too many inquisitive idiots."
pgpgOxa7r6HQ3.pgp
Description: OpenPGP digital signature
