mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Benoît BURNICHON" <Benoit.BURNICHON@airtag.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Runtime dependencies generation
Date: Wed, 16 Nov 2011 20:20:12 +0000	[thread overview]
Message-ID: <3944866A166FC34A948C72DD5EDDCA2A1DAE6C12@HQ0SBS01.airtag.local> (raw)

Hi all,

I have a package which I know depends on some options

This package is not compiled and just need to be installed (it contains only scripts)
In the KConfig file, I set up lines like:

        depends on BUSYBOX
        depends on COREUTILS_OD       || BUSYBOX_HEXDUMP
        depends on COREUTILS_READLINK || BUSYBOX_READLINK
        depends on COREUTILS_SORT     || BUSYBOX_SORT
        depends on COREUTILS_STAT     || (BUSYBOX_STAT && BUSYBOX_FEATURE_STAT_FORMAT)
        depends on DIFFUTILS_DIFF     || BUSYBOX_DIFF

Everything is fine for package generation. But, when I asks ipkg to tell me on what depends my package with:

$ ipkg whatdepends mypackage

I end up with no dependencies

I know that there are no compilation dependencies, but how can I tell ptxdist that the depends line should contain a specific runtime package dependency. Also, when such a dependency is enforced, one could set up a specific rule for the version needed (in my case, I'd like to add 'busybox > 1.17.1-4')

I would like to be able to install the package on the target without manually verifying that all the required packages are on it. Instead, I want to perform an 'ipkg update', 'ipkg upgrade', then 'ipkg install mypackage'.

Has anyone already faced this need?

Ben



________________________________

Ce courriel et toutes les pièces jointes sont confidentiels et peuvent être couverts par un privilège ou une protection légale. Il est établi à l’attention exclusive de ses destinataires. Toute utilisation de ce courriel non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse préalable.
This email and any attachment are confidential and may be legally privileged or otherwise protected from disclosure. It is intended only for the stated addressee(s) and access to it by any other person(s) is unauthorized. Any use, dissemination or disclosure not in accordance with its purpose, either in whole or in part, is prohibited without our prior formal approval.
-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2011-11-16 20:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 20:20 Benoît BURNICHON [this message]
2011-11-17  5:07 ` Robert Schwebel
2011-11-17 10:34   ` Benoît BURNICHON
2011-11-20 12:49     ` Michael Olbrich

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=3944866A166FC34A948C72DD5EDDCA2A1DAE6C12@HQ0SBS01.airtag.local \
    --to=benoit.burnichon@airtag.com \
    --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