All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] linuxconsoletools: new package
Date: Tue, 20 Jun 2017 15:19:36 +0200	[thread overview]
Message-ID: <87wp86eqzb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170620150550.7cbbae30@windsurf.lan> (Thomas Petazzoni's message of "Tue, 20 Jun 2017 15:05:50 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 >> What is the way forward? Drop the old package and add Config.in.legacy
 >> handling for the old symbols?

 > Thanks for pointing out, I didn't notice there was an overlap with our
 > input-tools package. Our input-tools package references
 > http://linuxconsole.sourceforge.net/ as  the upstream URL, which no
 > longer exists, and fetches a Debian package from 2010 called joystick.
 > All of this is a pretty confusing:

 > Buildroot package name != upstream URL project != Debian package name

 > Since linuxconsoletools provides the three utilities provided by
 > input-tools, has a name matching the upstream project, and uses a more
 > recent version, I would suggest to drop input-tools indeed, and add a
 > Config.in.legacy option that automatically enables linuxconsoletools.

Yes, I agree - The input-tools package is very old and hasn't been
updated in close to 10 years.

Will you send a patch to add the legacy handling or should I?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-06-20 13:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 16:55 [Buildroot] [PATCH v2 1/1] linuxconsoletools: new package Koen Martens
2017-06-19 19:44 ` Thomas Petazzoni
2017-06-19 19:51   ` Koen Martens
2017-06-19 20:08     ` Thomas Petazzoni
2017-06-20 12:08   ` Peter Korsgaard
2017-06-20 12:48     ` Koen Martens
2017-06-20 13:05     ` Thomas Petazzoni
2017-06-20 13:19       ` Peter Korsgaard [this message]
2017-06-20 13:35         ` Thomas Petazzoni
2017-06-20 18:35           ` Koen Martens
2017-06-20 19:02             ` Koen Martens

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=87wp86eqzb.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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.