Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alejandro del Castillo <alejandro.delcastillo@ni.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libsolv: add new recipe
Date: Wed, 9 Dec 2015 19:40:46 -0600	[thread overview]
Message-ID: <5668D81E.1040806@ni.com> (raw)
In-Reply-To: <1750958.3rdPrcUnoM@peggleto-mobl.ger.corp.intel.com>



On 12/09/2015 04:04 PM, Paul Eggleton wrote:
> So perhaps it was discussed elsewhere, but in any case if you want this to be
> added to OE-Core there needs to be something mentioned in the commit message
> about why - what needs this? If nothing, is OE-Core the best place for it?

To add a bit more color: opkg 0.3.1 has a new backend to use libsolv as the
dependency solver instead of using the recursive internal algorithm. 
Moving forward
(jethro + 2 probably) I envision OE using the libsolv backend by default 
since the libsolv solver is vastly superior to the internal one.

-- 
Cheers,

Alejandro


      parent reply	other threads:[~2015-12-10  1:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 20:50 [PATCH] libsolv: add new recipe Alejandro del Castillo
2015-12-09 22:04 ` Paul Eggleton
2015-12-09 23:01   ` [PATCH v2] " Alejandro del Castillo
2015-12-10 21:22     ` [PATCH v3] " Alejandro del Castillo
2015-12-10 23:16       ` Andre McCurdy
2015-12-10 23:55         ` Burton, Ross
2015-12-11  0:15           ` Martin Jansa
2015-12-11  8:48             ` Burton, Ross
2015-12-11 21:29         ` [PATCH v4] " Alejandro del Castillo
2015-12-11 21:32           ` Martin Jansa
2015-12-12  0:14             ` [PATCH v5] " Alejandro del Castillo
2015-12-10  1:40   ` Alejandro del Castillo [this message]

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=5668D81E.1040806@ni.com \
    --to=alejandro.delcastillo@ni.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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