mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de, Andreas Glatz <andi.glatz@gmail.com>
Subject: Re: [ptxdist] Can packages be build w/o installing them on the rootfs?
Date: Thu, 28 Sep 2017 14:12:34 +0100	[thread overview]
Message-ID: <a7b7fead-0c2a-2e7f-6c84-76b474386421@mev.co.uk> (raw)
In-Reply-To: <CAKJ14Ncay+n-y8HEwHwThycKmVXvbq8Ro+W8a_geLdZHPfjyWw@mail.gmail.com>

On 28/09/17 11:49, Andreas Glatz wrote:
> Hi
> 
> We have a platform application and one to three dynamic libraries
> that, if present, are loaded into the platform to extend its
> functionality. The finished product with be sold in three grades, base
> advanced and full. The base version should only contain the platform
> application, and base dynlib, the advanced version should only contain
> the platform application, and base + advanced dynlibs, ...
> 
> Our idea now is to have three ptxdist packages that depend on the
> platform application package:
> - base pkg: contains only the base dynlib
> - advanced pkg: contains only the base + adv dynlibs
> - full pkg: contains only the base + adv + full dynlibs
> 
> When we compile the rootfs we want all three packages built, but
> initially none installed on the rootfs. Is this possible somehow?

Perhaps you could use the "collections" feature.

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk> )=-
-=(                          Web: http://www.mev.co.uk/  )=-

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-09-28 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 10:49 Andreas Glatz
2017-09-28 13:12 ` Ian Abbott [this message]
2017-09-28 14:25   ` Juergen Borleis

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=a7b7fead-0c2a-2e7f-6c84-76b474386421@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=andi.glatz@gmail.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