On Thu, Nov 2, 2017 at 12:38 PM, Michael Olbrich
<m.olbr...@pengutronix.de> wrote:
> On Thu, Nov 02, 2017 at 01:20:17PM +0100, Guillermo Rodriguez Garcia wrote:
>> 2017-11-01 12:01 GMT+01:00 Michael Olbrich <m.olbr...@pengutronix.de>:
>> > 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?
> No, you need to use collections as well. There is some stuff about this in
> the documentation.

We had a similar use-case, albeit it wasn't for a hotfix package.

I think the steps to achieve your goal could be as follows:

(i) you mark your hotfix package as 'tristate' in the *.in file
(ii) you create a collection config that does NOT include the hotfix
package, e.g. using 'ptxdist menuconfig collection
(iii) run 'ptxdist go' (without any collection config link) to
generate all the packages + hotfix package
(iv) run 'ptxdist --collectionconfig=configs/mycollectionconfig images
=> creates the flash images, but w/o hotfix package applied

ptxdist mailing list

Reply via email to