On Wed, Nov 20, 2019 at 11:12:37PM +0100, Alexander Kanavin wrote: > The gettext problem is the immediate reason, but the broader reason is that > the code is not maintained, and we should try to avoid burdening the > project with unmaintained code. There's already 8 custom patches fixing > issues caused by lack of upstream maintenance, and the gettext certainly > won't be the last required fix. I have no interest in zmodem transfers, > thus I opted for recipe removal.
I don't in general buy the line of argument that "I have no interest in X, and I want to make some change that happens to break X, ergo X should be removed", but in this particular case it probably is true that lrzsz has few enough users that it wouldn't qualify for inclusion in oe-core if someone were trying to add it nowadays. So if it represents a net maintenance burden then, although I do still use it myself from time to time, I would be OK with it being removed from oe-core. However, I think the point still stands that the commit message needs to provide a better description of why the package is being removed. If you think it represents an ongoing maintenance headache that's already bad and only going to get worse, and this now outweighs its usefulness, let's just say that. Not all old software is problematic, and not all problematic software is old; the fact that the last release was 20 years ago is an interesting fact but in isolation that doesn't represent a problem. Indeed, compared to some other packages in oe-core, eight patches in total over a 20-year period doesn't seem like that bad of an average. p. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
