On 20/11/2019 23:18, Adrian Bunk wrote:
On Wed, Nov 20, 2019 at 11:56:38PM +0100, Alexander Kanavin wrote:
On Wed, 20 Nov 2019 at 23:32, Phil Blundell <[email protected]> wrote:
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.
Fair enough, I wrote a hasty commit message. Mistakes happen.
Can I say what my problem is? Here goes: so far, no one in this discussion
offered actual help with the actual issue. If you need this or that
functionality from Yocto, please try to place help ahead of complaints and
criticism.
No, your problem is your way of communication.
It is a very unfriendly way of communication to request help in the form
patch aiming at immediate removal.
Hopefully everyone has calmed down overnight and we can continue this
discussion politely?
Yes, Alex's commit message should have spelt out that both:
1) there are doubts anyone is actually using zmodem still (he did this)
2) the source is positively ancient and building it on modern linux is
getting harder over time (this was implied by being in a series that
upgraded gettext and fixed other recipes, instead of being spelt out).
So, if zmodem is still a useful feature to have in core, then is anyone
willing to step up and either:
1) maintain the recipe. I'd love someone who uses lrzsz to put a fork
up on github, integrate all of our patches, and start maintaining it.
Maybe then other distributions who still ship it will join in too.
2) provide an alternative.
Ross
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
