Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Böszörményi Zoltán" <zboszor@pr.hu>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] package: Record PE and PR values for shlib dependencies
Date: Sun, 14 Jan 2018 11:27:21 +0000	[thread overview]
Message-ID: <1515929241.29722.212.camel@linuxfoundation.org> (raw)
In-Reply-To: <20180112134659.5793-1-zboszor@pr.hu>

On Fri, 2018-01-12 at 14:46 +0100, Böszörményi Zoltán wrote:
> When downgrading a package or using a substitute with lower version,
> the way to do it is adding or increasing PE and there may be other
> reasons to set PE.
> 
> But it doesn't directly help dependant packages because the shlib
> records only contain PV.
> 
> Let's add the PE value into the shlib records for packages where
> it's set.
> 
> The in-memory variables storing the versions now use the PE:PV
> notation but the on-disk files must use something else because
> the : character is already used as field delimiter in the
> package.list
> files storing the shlib records. Use # instead in the files,
> so the file format doesn't change. Conversion occurs on reading
> and writing the package.list files.

Can you explain a bit more about why/how this causes a problem?

PE is needed to maintain consistency of package feeds but the shlibs
code is primarily used for build time dependency analysis to figure out
which packages need to depend upon what and ensure runtime dependencies
are met. I'm not sure that should care about PE.

For PR, again its primarily for package feeds so that updates are
detected and I'm not sure why the shlibs code should need to care about
it.

Perhaps if you explain more about the issues you're having which this
fixes I'll better understand the problem/need.

Cheers,

Richard



  reply	other threads:[~2018-01-14 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 13:46 [PATCH v2] package: Record PE and PR values for shlib dependencies Böszörményi Zoltán
2018-01-14 11:27 ` Richard Purdie [this message]
2018-01-16 10:10   ` Böszörményi Zoltán
2018-01-19 13:20     ` Böszörményi Zoltán

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=1515929241.29722.212.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=zboszor@pr.hu \
    /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