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] How to create "hotfix" packages
Date: Wed, 1 Nov 2017 12:01:05 +0100	[thread overview]
Message-ID: <20171101110105.diihar3apnoooszg@pengutronix.de> (raw)
In-Reply-To: <CABDcavZmoCage6_HYdBbjq5E9Oq0g3YPMb545bg3Z8EMxfm5-g@mail.gmail.com>

Hi,

On Tue, Oct 31, 2017 at 06:28:14PM +0100, Guillermo Rodriguez Garcia wrote:
> For a ptxdist BSP I am managing I need to create a "hotfix" package to
> patch a number of files on already deployed devices.
> 
> This package will only be used on devices which are already deployed, and
> its files should not be part of the rootfs images if the platform is
> rebuilt. Is it possible to have ptxdist build an .ipk package that will not
> be included in the filesystem images ?
> 
> I was hoping that marking the package as "M" in ptxdist menuconfig would do
> the trick :) but that doesn't do what I thought.

It can be used like that, but for a single package, it's a bit complex.
If you use the regular images, then you can create a "lazy" package.
Just create a normal package and then modify the makefile like this:
"PACKAGES-$(PTXCONF_..." -> "LAZY_PACKAGES-$(PTXCONF_..."

The package will not be added to the rootfs, however, it will not be built
by default either. So you need to run "ptxdist targetinstall <pkg-name>" to
build it.

Regards,
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:[~2017-11-01 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 17:28 Guillermo Rodriguez Garcia
2017-11-01 11:01 ` Michael Olbrich [this message]
2017-11-02 12:20   ` Guillermo Rodriguez Garcia
2017-11-02 12:38     ` Michael Olbrich
2017-11-02 14:09       ` Andreas Glatz
2017-11-02 15:19       ` Guillermo Rodriguez Garcia
2017-11-02 15:33         ` Michael Olbrich
2017-11-02 15:50           ` Guillermo Rodriguez Garcia

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=20171101110105.diihar3apnoooszg@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