packager stops unexpectedly

I was trying to package a custom build of vim. I’ve moved all
interested files into a basedir and started packager as usual:

$ ls
basedir
$ packager basedir

Packager will now create a set of packages for use with the Package
Installer.

Please supply the necessary information to build the Package Manifest
file.
Default values are shown in parentheses (like this), and selected by
hitting
ENTER. Type Ctrl-B on its own, then ENTER, to return to the previous
question.

------File Searching------


Error during generation. Packages not generated.
(operator chose to abort packager)

Searching for all files to include… $ # back in the shell

Packager stops without any user intervention.
I’ve detected that packager stops when encouters the /usr/share
subdirectory. So I’ve tried to manually remove file-by-file to see
exactly in which file hangs but there was too many files.
I can’t debug it, so what can I do?

Is there some quick way to include an entire directory using a single
QPG:Add rule?

Cheers


Wave++

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

I was trying to package a custom build of vim. I’ve moved all
interested files into a basedir and started packager as usual:

$ ls
basedir
$ packager basedir

Packager will now create a set of packages for use with the Package
Installer.

Please supply the necessary information to build the Package Manifest
file.
Default values are shown in parentheses (like this), and selected by
hitting
ENTER. Type Ctrl-B on its own, then ENTER, to return to the previous
question.

------File Searching------

Error during generation. Packages not generated.
(operator chose to abort packager)

Searching for all files to include… $ # back in the shell

Packager stops without any user intervention.
I’ve detected that packager stops when encouters the /usr/share
subdirectory. So I’ve tried to manually remove file-by-file to see
exactly in which file hangs but there was too many files.
I can’t debug it, so what can I do?

Can you tar up and send me the /usr/share directory? I can try
to debug it in the office.

Is there some quick way to include an entire directory using a single
QPG:Add rule?

Yes: <QPG:Add type=“tree” file=“basedir” install="/"/>

Jerry Chappell

Jerry Chappell <jchappell@qnx.com> wrote:

Can you tar up and send me the /usr/share directory? I can try
to debug it in the office.

I’ve detected the problem when I was making a tarball of the directory.
A directory was set unreadable (!) and packager wasn’t able to
descend into it:

tar: Cannot add file usr/share/vim/vim60/tools/CVS/Root: Permission denied

Maybe a more descriptive error… :slight_smile:

Another little question: does packager use the “file” tool to determine
the file type or uses some internal mechanism?
If so, changing the magic file affects packager?


Wave++

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

Another little question: does packager use the “file” tool to determine
the file type or uses some internal mechanism?
If so, changing the magic file affects packager?

Packager uses ‘objdump’ to determine any shared objects required or
provided by your files. It uses the ‘elf’ headers to determine what
type (and what processor) the file is. It also uses the ‘strip’ utility to
remove any debugging information, etc. in your files.

Jerry Chappell