I downloaded the packager utility last night, and attempted to package up
source navigator. I answered a lot of questions, pakager then went and
displayed a progress indication in percent, and it got through to 100%.and
then right at the end packager went into a loop asking me the same questions
over and over again. Finally I ctrl-c’d out, and wa left with nothing in my
current directory. I then did a find on / looking for anything with the
name of the package in it, and I found that packager had created a tree
under /tmp/KJASD23423 (where KJASD23423 is a fictional temporary filename).
I then copied the tree to my home directory, and gzipped and tarred the tree
from “core-*” on down and renamed the file *.qpk, I then copied the MANIFEST
that packager had generated to a *.qpm file. I then tried pkg-installer
against it, and it looks good.
So the question I have is where in the process was packager when it went
into a loop, and does anyone have any idea why it did that ?
Thanks.
Rennie
“John Doe” <john@csical.com> wrote in message
news:<96h5ni$s7k$3@inn.qnx.com>…
I downloaded the packager utility last night, and attempted to package up
source navigator. I answered a lot of questions, pakager then went and
displayed a progress indication in percent, and it got through to 100%.and
then right at the end packager went into a loop asking me the same
questions
over and over again. Finally I ctrl-c’d out, and wa left with nothing in
my
current directory. I then did a find on / looking for anything with the
name of the package in it, and I found that packager had created a tree
under /tmp/KJASD23423 (where KJASD23423 is a fictional temporary
filename).
The big question is this – what questions did it ask you all over again?
At the end of the package questions, it will produce a number of qpks and
then ask a pair of questions about launch items and scripts for each of
these packages. If you were packaging a development suite you may end up
with up to six packages to handle the cross development implications. What
you may have seen is some specialized questions for each package.
If that’s not the case – can you tell me what source you were building? Is
this reproduceable?
I then copied the tree to my home directory, and gzipped and tarred the
tree
from “core-*” on down and renamed the file *.qpk, I then copied the
MANIFEST
that packager had generated to a *.qpm file. I then tried pkg-installer
against it, and it looks good.
Well, I’m glad that you managed to make a package out of these temporary
files – I’m also sorry that it had to be a less than desirable experience.
Besides this, were there any other comments or problems?
-William Bull