All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: To be removed recipes
Date: Mon, 11 Dec 2006 21:50:15 +0100	[thread overview]
Message-ID: <200612112150.15571.openembedded@hrw.one.pl> (raw)
In-Reply-To: <1165789899.5604.43.camel@localhost.localdomain>

Dnia niedziela, 10 grudnia 2006 23:31, Richard Purdie napisał:
> On Fri, 2006-12-08 at 17:59 +0100, Michael 'Mickey' Lauer wrote:
> > Richard Purdie wrote:

> > >> Package Name:   bluez*2.*
> > >> Reason:         Obsolete by, and conflicts with bluez 3.7
> > >
> > > Fine with me.
> >
> > This can be a problem for Opie, since we used the no-dbus version for
> > quite some time to save space.
>
> In that case we can't remove the no-dbus version needed by opie.

Does someone tested OPIE with dbus version at all? How much does extra 
packages take etc? Without such testing sentence 'do not remove 
bluez*nodbus because OPIE needs it' does not have sense.

I also would like to get rid of bluez 2.x because it will be unmaintained 
software soon due to fact that everyone switched to 3.x versions.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

         You can close your eyes to reality, but not to memories.





  reply	other threads:[~2006-12-11 20:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27 16:09 To be removed recipes Koen Kooi
2006-12-07 12:38 ` Koen Kooi
2006-12-07 13:09   ` Richard Purdie
2006-12-08 16:11     ` Paul Sokolovsky
2006-12-11 20:52       ` Marcin Juszkiewicz
2006-12-08 16:59     ` Michael 'Mickey' Lauer
2006-12-10 22:31       ` Richard Purdie
2006-12-11 20:50         ` Marcin Juszkiewicz [this message]
2006-12-11 21:26           ` Paul Sokolovsky
2006-12-12 13:47     ` Marcin Juszkiewicz
2006-12-16 10:55     ` Koen Kooi
2006-12-16 14:23       ` Robert Woerle
  -- strict thread matches above, loose matches on Subject: below --
2006-12-18  9:08 Martyn Welch
2006-12-18 11:59 ` Rolf Leggewie

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=200612112150.15571.openembedded@hrw.one.pl \
    --to=openembedded@hrw.one.pl \
    --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.