All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Ross Burton <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 08/11] lrzsz: remove the recipe
Date: Thu, 21 Nov 2019 17:36:10 +0200	[thread overview]
Message-ID: <20191121153610.GA28013@localhost> (raw)
In-Reply-To: <238a39c7-b794-aaa0-1da6-4b585078f447@intel.com>

On Thu, Nov 21, 2019 at 09:24:34AM +0000, Ross Burton wrote:
>...
> 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.
>...

In embedded development there are some usecases left for this codebase 
from the 1980s that implements protocols that were widely popular in
the 1980s and early 1990s.

Ancient code implementing obsolete ancient stuff is not fun to maintain.


There are also two higher level topics that should be discussed:

1. Removal of maintainers.inc
There is some nitpicking that every recipe needs a maintainer.
For the package in question the maintainer is not involved in the 
discussion, and doesn't seem to have been asked for support or
asked regarding the suggested removal.

2. Who is responsible for fixing gettext breakages in meta-oe?
Alexander or Khem?


> Ross

cu
Adrian


  parent reply	other threads:[~2019-11-21 15:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 13:44 [PATCH 01/11] man-pages: correct the SRC_URI Alexander Kanavin
2019-11-20 13:44 ` [PATCH 02/11] man-pages: update to 5.03 Alexander Kanavin
2019-11-20 13:44 ` [PATCH 03/11] dummy-sdk-package.inc: do not include files into RREPLACES Alexander Kanavin
2019-11-23 14:37   ` Richard Purdie
2019-11-20 13:44 ` [PATCH 04/11] gettext-minimal-native: update to 0.20.1 Alexander Kanavin
2019-11-20 13:44 ` [PATCH 05/11] gettext: " Alexander Kanavin
2019-11-20 13:44 ` [PATCH 06/11] e2fsprogs: fix build issues with the latest version of gettext Alexander Kanavin
2019-11-20 13:44 ` [PATCH 07/11] console-tools: remove the recipe Alexander Kanavin
2019-11-20 13:44 ` [PATCH 08/11] lrzsz: " Alexander Kanavin
2019-11-20 19:49   ` Adrian Bunk
2019-11-20 20:00     ` Alexander Kanavin
2019-11-20 20:17       ` Adrian Bunk
2019-11-20 21:12         ` Alexander Kanavin
2019-11-20 21:38       ` Phil Blundell
2019-11-20 22:12         ` Alexander Kanavin
2019-11-20 22:32           ` Phil Blundell
2019-11-20 22:56             ` Alexander Kanavin
2019-11-20 23:18               ` Adrian Bunk
2019-11-21  9:24                 ` Ross Burton
2019-11-21 10:10                   ` Richard Purdie
2019-11-21 13:59                     ` Phil Blundell
2019-11-22  0:49                       ` Ross Burton
2019-11-25 12:07                       ` Ross Burton
2019-11-26 11:59                         ` Phil Blundell
2019-11-26 12:06                           ` Phil Blundell
2019-11-26 14:49                             ` Ross Burton
2019-11-27 14:32                           ` Ross Burton
2019-11-27 15:07                             ` Phil Blundell
2019-11-21 15:36                   ` Adrian Bunk [this message]
2019-11-21 16:41                     ` Richard Purdie
2019-11-20 13:44 ` [PATCH 09/11] p11-kit: convert to meson Alexander Kanavin
2019-11-23 23:04   ` Richard Purdie
2019-11-25 16:53     ` Alexander Kanavin
2019-11-20 13:44 ` [PATCH 10/11] mc: backport a patch to fix builds with latest gettext Alexander Kanavin
2019-11-20 13:44 ` [PATCH 11/11] systemtap: update to 4.2 Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191121153610.GA28013@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.