All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v4 2/2] systemd: conditionally RRECOMMENDS kbd*
Date: Fri, 20 Jan 2012 08:30:22 +0100	[thread overview]
Message-ID: <jfb56e$f67$1@dough.gmane.org> (raw)
In-Reply-To: <CAP9ODKoOkSrjWi27BT2Rv9v5oM37fP5fL5oLH8oDB54QJLdczg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 20-01-12 04:33, Otavio Salvador schreef:
> On Thu, Jan 19, 2012 at 20:03, Koen Kooi <koen@dominion.thruhere.net>
> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Op 19-01-12 20:53, Anders Darander schreef:
>>> Let the distro define a keyboard distro feature, to conditionally 
>>> include kbd*. (Headless distros might not want to RRECOMMENDS kbd*).
>> 
>> DISTRO_FEATURES is the wrong thing for that, so I'm going to NAK it.
>> 
> 
> What would be your suggestion for this then? I see no other alternative 
> then distro feature.

See what needs kbd and split it out, like we did with vconsole. Actually...
git grep implies that vconsole is the bit that needs kbd :)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAk8ZGAoACgkQMkyGM64RGpECJwCgi/yMgovhSMHJQnKmuzJR5xfn
YZQAn2ck7oLsFxPphCh2ijCalBdWcIK+
=BSEa
-----END PGP SIGNATURE-----




  reply	other threads:[~2012-01-20  7:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 19:52 [meta-oe][PATCH v4 0/2] systemd: package split Anders Darander
2012-01-19 19:53 ` [meta-oe][PATCH v4 1/2] systemd: split out systemd-analyze Anders Darander
2012-01-20  3:35   ` Otavio Salvador
2012-01-19 19:53 ` [meta-oe][PATCH v4 2/2] systemd: conditionally RRECOMMENDS kbd* Anders Darander
2012-01-19 22:03   ` Koen Kooi
2012-01-20  3:33     ` Otavio Salvador
2012-01-20  7:30       ` Koen Kooi [this message]
2012-01-20  8:01         ` Anders Darander
2012-01-20 11:30           ` Koen Kooi
2012-01-20 12:19             ` Anders Darander

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='jfb56e$f67$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.