packaging stories 2: packager strikes again

I’ve tried to package an update of an existing product but when I try
to install it, pkg-installer doesn’t show the already installed
version.

I’ve done a diff of the two qpm generated files:
7,8c7,8
< QPM:PackageNametest-1.0-public</QPM:PackageName>
< QPM:PackageSize1784</QPM:PackageSize>

QPM:PackageName>test-1.0.1-public</QPM:PackageName
QPM:PackageSize>512</QPM:PackageSize
10c10,11

<
QPM:PackageReleaseDate2001/09/07</QPM:PackageReleaseDate>

QPM:PackageReleaseDate>2001/09/15</QPM:PackageReleaseDate

12c13
< QPM:FileVersion1.00</QPM:FileVersion>

QPM:FileVersion>1.00</QPM:FileVersion
17c18

< QPM:ProductSize1083</QPM:ProductSize>

QPM:ProductSize>6144</QPM:ProductSize
32c33

<
QPM:InstallPathpublic/test/core-1.0</QPM:InstallPath>

QPM:InstallPath>public/test/core-1.0.1</QPM:InstallPath

36,38c37,39
< QPM:ReleaseDate2001/09/07</QPM:ReleaseDate>
< QPM:ReleaseVersion1.0</QPM:ReleaseVersion>

QPM:ReleaseDate>2001/09/15</QPM:ReleaseDate
QPM:ReleaseVersion>1.0.1</QPM:ReleaseVersion

It seems to be correct. Only product size/release version/package
name changes. The product identifier is the same. Certainly something
else must be set to show the version of the already installed package.
But what?

For example, if I change ONLY the package build or version build
informations, pkg-installer shows up the installed package version
and correctly removes the previous one.

Another question rises up: what happens if I try to install the
aftermentioned package (which pkg-installer seem to ignore the
correlation with the old version) as it includes conflicting files?
Old package can’t coexist with the newer one. Does the old package be
removed or at least deactivated before the installation?


Wave++

Wave++ <wavexx@apexmail.com> wrote:

I’ve tried to package an update of an existing product but when I try
to install it, pkg-installer doesn’t show the already installed
version.

There may be a problem still in pkg-installer, where newer versions
do not show up as updates to older versions.

If you can email me the packages you have (old, and new), I can try
to figure out what’s happening with them.

I believe we can fix the problem without an upgrade to pkg-installer,
so if you send me your QPG too, I can add the lines necessary to
make the fix for you.

Don’t know what a QPG is? Glad you asked! Check out part 2 of my
QDN article:

http://qdn.qnx.com/articles/sep1401/index.html

which explains the use of QPG files, and has links to the required
documentation.

Jerry Chappell
jchappell@qnx.com

Jerry Chappell a écrit :

Wave++ <> wavexx@apexmail.com> > wrote:
I’ve tried to package an update of an existing product but when I try
to install it, pkg-installer doesn’t show the already installed
version.

There may be a problem still in pkg-installer, where newer versions
do not show up as updates to older versions.

If you can email me the packages you have (old, and new), I can try
to figure out what’s happening with them.

I believe we can fix the problem without an upgrade to pkg-installer,
so if you send me your QPG too, I can add the lines necessary to
make the fix for you.

Don’t know what a QPG is? Glad you asked! Check out part 2 of my
QDN article:

http://qdn.qnx.com/articles/sep1401/index.html

which explains the use of QPG files, and has links to the required
documentation.

Jerry Chappell
jchappell@qnx.com

Hi Jerry,
Did you find something about included libraries dependencies?

Thanks,
Alain.

Jerry Chappell a écrit :

Wave++ <> wavexx@apexmail.com> > wrote:
I’ve tried to package an update of an existing product but when I try
to install it, pkg-installer doesn’t show the already installed
version.

There may be a problem still in pkg-installer, where newer versions
do not show up as updates to older versions.

If you can email me the packages you have (old, and new), I can try
to figure out what’s happening with them.

I believe we can fix the problem without an upgrade to pkg-installer,
so if you send me your QPG too, I can add the lines necessary to
make the fix for you.

Don’t know what a QPG is? Glad you asked! Check out part 2 of my
QDN article:

http://qdn.qnx.com/articles/sep1401/index.html

which explains the use of QPG files, and has links to the required
documentation.

Jerry Chappell
jchappell@qnx.com

I didn’t understand the paragraph about:
<QPG:Add file=“sym_link_name” install="/opt/bin/" filetype=“symlink”
linkto=“file/to/link/to”/>

tag.

Why symbolic links are not automatically included in qpg files when they
are included in the qpr file during initial package session?

Thanks,
Alain.