Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] move to opkg
Date: Sun, 23 Mar 2008 23:06:19 +0000	[thread overview]
Message-ID: <1206313579.4529.85.camel@dax.rpnet.com> (raw)
In-Reply-To: <47E5A67B.5030809@dls.net>

I'm not going to comment specifically on the various aspects of this
thread, it makes depressing reading and I can sympathise with the
various sides.

Yes, there is a strong desire to remove ipkg from OE entirely from
certain parties and the reasons are political and complicated since
there is a lot of history involved. Personally I'm on the fence, ipkg is
a known quantity, bugs and all but I can see benefits of opkg.

Personally I wasn't particularly keen on changing Poky but others were
and I have other things that I feel more strongly about to expend energy
on so Poky changed. I don't have a problem with the changes in Poky, I'm
not sure that change should have rolled into OE quite as quickly
however.

The main problem is the situation that OE has left some distributions
in. Opkg is not compatible with ipkg despite their similarities due to
the changed files locations. We've therefore just forced a massive ABI
change on users and I'm not sure the consequences have been considered
and it did need more discussion than it got :/. Solutions to the issues
were certainly not mentioned in the discussion although I did hint at
the problems.

Where do we go from here?

Judging from the comments we have some people who want to continue to
use ipkg, is OE.dev going to support that? I know what several people
are going to answer and there is going to be a conflict here :(. There
is no technical reason both ipkg and opkg can't be in OE.dev with the
appropriate magic.

This does raise the question of whether basing a distribution directly
off .dev is a good idea? I know some people do, I also know its called
the OE development branch for a reason.

The thing is I don't think this is a technical problem, its more a
question about how OE.dev is managed and who can do what and how. If we
all had to write down the aims and objectives of OE.dev, every one would
be different :/.

I could wade into this discussion as I've done in others but I don't
particularly want to and I'd prefer to let someone else deal with it.
I've already wasted far too much time trying to type this so far, this
is about the 3rd version since I'm not getting across what I think is
the right message to all parties :/.

The battering I've had recently on list, off list and on irc are enough
to make me seriously consider why I do what I do and whether I want to
continue doing it.

Richard - wishing everyone could coexist




  parent reply	other threads:[~2008-03-23 23:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  8:55 [RFC] move to opkg Koen Kooi
2008-03-18  9:55 ` Junqian Gordon Xu
2008-03-19 15:33   ` WPkg Silvano Catinella
2008-03-25 17:23     ` WPkg Michael 'Mickey' Lauer
2008-03-25 23:42       ` WPkg Rod Whitby
2008-04-01  9:15         ` WPkg Silvano Catinella
2008-03-18  9:56 ` [RFC] move to opkg Marcin Juszkiewicz
2008-03-18 10:09   ` Koen Kooi
2008-03-18 10:42     ` Koen Kooi
2008-03-18 11:34       ` Jacob Thebault-Spieker
2008-03-18 11:42 ` Koen Kooi
2008-03-18 13:49 ` Geoffrey Wossum
2008-03-18 14:32   ` Koen Kooi
2008-03-18 16:48     ` Richard Purdie
2008-03-18 17:05       ` Koen Kooi
2008-03-23  0:38         ` Mike (mwester)
2008-03-23  5:17           ` Mike (mwester)
2008-03-23 10:43             ` Marcin Juszkiewicz
2008-03-23 11:02             ` Koen Kooi
2008-03-23 13:25               ` Mike (mwester)
2008-03-23 18:18               ` Tom Rini
2008-03-23 18:55                 ` Koen Kooi
2008-03-23 22:20                   ` Tom Rini
2008-03-23 23:10                     ` Rod Whitby
2008-03-23 23:06           ` Richard Purdie [this message]
2008-03-23 23:46             ` Rod Whitby
2008-03-24  4:30             ` Mike (mwester)
2008-03-24  7:55               ` Stelios Koroneos
2008-03-18 18:12     ` Tom Rini
2008-03-18 18:18       ` Mikhail Gusarov
2008-03-18 18:40         ` Koen Kooi
2008-03-19  9:06           ` Richard Purdie
2008-03-19  9:13             ` Marcin Juszkiewicz
2008-03-18 14:35   ` Marcin Juszkiewicz
2008-03-18 22:00 ` Koen Kooi
2008-03-19 17:52 ` [RFC] move to opkg / md5 error on big-endian machine Jeremy Lainé
2008-03-22 20:38   ` Jeremy Lainé
2008-03-23 10:59 ` [RFC] move to opkg Jeremy Lainé

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=1206313579.4529.85.camel@dax.rpnet.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox