mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Specific version dependency in opkg/ipkg Depends field
Date: Wed, 3 Aug 2016 09:57:08 +0200	[thread overview]
Message-ID: <20160803075708.GE11824@pengutronix.de> (raw)
In-Reply-To: <CAKJ14NdUYhgoA3tm+VpiQyFo1zq=TtFMG83d3_JvMiWwtvC_dA@mail.gmail.com>

Hi,

On Tue, Aug 02, 2016 at 04:22:24PM +0100, Andreas Glatz wrote:
> I'm using ptxdist-2012.03.0 and I'm adding two new components to the
> standard installation. Everything seems to work fine and I get ipkgs
> for both components, which I can install on the target.
> 
> Now I'd like to create a dependency of component A on B so that A can
> only be installed if B is present and has a certain version, let's say
> B has to be at or newer than version 0.6. Opkg/Ipkg seem to support
> this with by e.g. adding B(>=0.6) to Depends field in the control file
> of ipkg A.
> 
> Ptxdist automatically appends dependencies, however I haven't found a
> way to add a version dependency to a package (without hacking the
> package after it was created).
> 
> Any help appreciated.

There is no easy way to do this. In theory you could overwrite
ptxd_make_xpkg_prepare() with a custom version and do whatever you want
there, but accessing the necessary information there will not be trivial.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2016-08-03  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02 15:22 Andreas Glatz
2016-08-03  7:57 ` Michael Olbrich [this message]
2016-08-03  8:42   ` Andreas Glatz

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=20160803075708.GE11824@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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