Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 04/10] dbus-glib: include bash-completion stuff
Date: Sun, 25 Sep 2011 19:48:18 +0200	[thread overview]
Message-ID: <20110925174817.GA3663@ad.chargestorm.se> (raw)
In-Reply-To: <CAP9ODKquVa1GNpKfchhExqswpYSY+qYFAmqQQcx4HHmP4LUupA@mail.gmail.com>

* Otavio Salvador <otavio@ossystems.com.br> [110925 19:34]:
> On Sun, Sep 25, 2011 at 14:20, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Fri, 2011-09-23 at 17:09 -0300, Otavio Salvador wrote:
> >> On Fri, Sep 23, 2011 at 16:46, Dmitry Eremin-Solenikov
> >> <dbaryshkov@gmail.com> wrote:
> >> ...
> >> > +FILES_${PN} = "${libdir}/lib*.so.* \
> >> > +               ${sysconfdir}/bash_completion.d/dbus-bash-completion.sh \
> >> > +              ${libexecdir}/dbus-bash-completion-helper"
> >> ...

> >> I'd prefer to have this in another package.

> > Me too, I think this should be packaged separately (with a RRECOMMENDS
> > on bash-completion for good measure).

> I don't think RRECOMMENDS are good in this case; people were using it
> without this for long time and noone has noticed yet so it seems not
> that required.

I think Richard meant that the new dbus-glib-bash-completion(?) package
should have a RRECOMMENDS on bash-completion (as it will be pretty
useless on a system without bash-completion).

Dbus-glib should definitely not start to RRECOMMEND bash-completion, as
noone has requested that for a long time.

Cheers,
Anders

-- 
Anders Darander
ChargeStorm AB / eStorm AB



  parent reply	other threads:[~2011-09-25 17:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23 19:46 [PATCH 01/10] default-provider: also define a default provider for gconf-native Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 02/10] bitbake.conf: change ccache path to use MULTIMACH_HOST_SYS Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 03/10] bash-completion: new recipe Dmitry Eremin-Solenikov
2011-09-25  9:46   ` Richard Purdie
2011-09-23 19:46 ` [PATCH 04/10] dbus-glib: include bash-completion stuff Dmitry Eremin-Solenikov
2011-09-23 20:09   ` Otavio Salvador
2011-09-25 17:20     ` Richard Purdie
2011-09-25 17:34       ` Otavio Salvador
2011-09-25 17:44         ` Richard Purdie
2011-09-25 17:48         ` Anders Darander [this message]
2011-09-23 19:46 ` [PATCH 05/10] eglibc: fix packaging of some of nativesdk packages, V2 Dmitry Eremin-Solenikov
2011-09-25 17:22   ` Richard Purdie
2011-09-23 19:46 ` [PATCH 06/10] icecc-create-env-native: provide the script right in the tree Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 07/10] gcc: fix possible problems with nscd compilation during eglibc-nativesdk build Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 08/10] gcc: include libgcov.a into libgcc-dev package Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 09/10] gconf-dbus: packaging fixup Dmitry Eremin-Solenikov
2011-09-23 19:46 ` [PATCH 10/10] libffi: really populate -dev package Dmitry Eremin-Solenikov
2011-09-26 12:11 ` [PATCH 01/10] default-provider: also define a default provider for gconf-native Dmitry Eremin-Solenikov
2011-09-26 12:41   ` Richard Purdie

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=20110925174817.GA3663@ad.chargestorm.se \
    --to=anders@chargestorm.se \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox