All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: To be removed recipes
Date: Thu, 07 Dec 2006 13:09:03 +0000	[thread overview]
Message-ID: <1165496944.5601.32.camel@localhost.localdomain> (raw)
In-Reply-To: <45780B2E.4020906@dominion.kabel.utwente.nl>

On Thu, 2006-12-07 at 13:38 +0100, Koen Kooi wrote:
> > In case people didn't notice,
> > http://www.openembedded.org/repo/org.openembedded.dev/removal.txt has a few entries now,
> > which will be removed on the specified dates.
> 
> Only 5 days left till the first batch gets removed.

> Package Name:   Maemo
> Reason:         Unfetchable, obsoleted by IT2006 release.

I don't know what we should do with these for the best. The end result
will be maemo being near enough totally removed from OE which sends out
the wrong message. I would ultimately like to see maemo in OE...

Maybe a contender for moving to non-working?

> Package Name:   task-bootstrap*
> Reason:         Obsoleted by task-base

Have we anyone still using this? I'm nervous removing this just yet...

> Package Name:   bluez*2.*
> Reason:         Obsolete by, and conflicts with bluez 3.7               

Fine with me.

> Package Name:   mono
> Reason:         Obsolete version - 1.2 is current, 1.0 is not fetchable

non-working - ultimately we probably want mono
 
> Package Name:   zeecookbook
> Reason:         Not maintained upstream, not fetchable

Fine with me.

> Package Name:   qpe-vexed
> Reason:         Not fetchable, all search results points to OE related infos

Fine with me.

> Package Name:   ipac-ng
> Reason:         Depends on libgd-perl which is not in metada

> Package Name:   
? (there are two of these)
 
> Package Name:   nsqld
> Reason:		Never used

Fine with me.

> Package Name:   gpe-mileage
> Reason:         Unfinished, no development progress

Fine with me.




  reply	other threads:[~2006-12-07 13:10 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 [this message]
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
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=1165496944.5601.32.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.