All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Commit 2fdf1aa1c869ea9deecee86206f49a2eca9d7c00 breaks opkg
Date: Thu, 03 Dec 2009 21:25:17 -0600	[thread overview]
Message-ID: <4B18811D.8020206@mwester.net> (raw)

Commit 2fdf1aa1c869ea9deecee86206f49a2eca9d7c00 (Koen) breaks
opkg-nogpg-nocurl.  I have no idea what else might be broken, but the
fact that it removes all the critical patches that make it work on
small-memory machines is the most obvious cause of the breakage.

So what do you all want me to do about this?  We can revert the commit. 
Or someone can try to sort out a way to let opkg change without
impacting the tiny-memory version of opkg (which will get more and more
difficult as the two diverge).  Or I can just create
opkg-nogpg-nocurl-slugos.bb in hopes that it won't get stomped on.

Thanks,
Mike (mwester)



             reply	other threads:[~2009-12-04  3:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-04  3:25 Mike Westerhof [this message]
2009-12-04  4:53 ` Commit 2fdf1aa1c869ea9deecee86206f49a2eca9d7c00 breaks opkg Graham Gower
2009-12-04  8:40   ` Andrea Adami
2009-12-04 14:09     ` Mike Westerhof
2009-12-04 14:20   ` Mike Westerhof
2009-12-04 14:56     ` Dr. Michael Lauer
2009-12-04 15:05     ` Marcin Juszkiewicz

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=4B18811D.8020206@mwester.net \
    --to=mike@mwester.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.