From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] How to create "hotfix" packages
Date: Thu, 2 Nov 2017 13:20:17 +0100 [thread overview]
Message-ID: <CABDcavYgJuyVNVmVKBusHZfD55dchwJZnuCPiJi4Dv3HDVPVzQ@mail.gmail.com> (raw)
In-Reply-To: <20171101110105.diihar3apnoooszg@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1547 bytes --]
Hello Michael,
2017-11-01 12:01 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> 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.
>
Do you marking the package as "M"? I tried that but it seems to do exactly
the same as when I just enable it (with "*"). Am I missing something?
> 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.
>
But then when I do ptxdist targetinstall <pkg-name>, the .ipk will be
built, but will the files also be added to sysroot? The latter is what I
would like to avoid...
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 2394 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-11-02 12:20 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
2017-11-02 12:20 ` Guillermo Rodriguez Garcia [this message]
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=CABDcavYgJuyVNVmVKBusHZfD55dchwJZnuCPiJi4Dv3HDVPVzQ@mail.gmail.com \
--to=guille.rodriguez@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