Rodney Lott <firstname.lastname@example.org> wrote:
: Thanks for the info on the .qpm and .qpk stuff, Thomas.
A little late, but better than never =;-)
: I have a few conceptual questions, then:
: Is there any documentation or tools that would allow me,
: or any third party developer, to take some software in a tar.gz format
: and generate the appropriate .qpm, .qpk, and (if necessary) .qrm files?
: I know that the .qpk file is just a renamed .tar.gz, so that is not
Actually the whole process is more tedious than it is difficult.
It is simply a matter of taking your software, laying it out in
a directory structure that you want it to conform to, creating
one XML file which describes the relationship of this software
(see MANIFEST files in the /pkgs/… directory). There are
two main components to a MANIFEST file (and subsequently a
qpm file). The first is the information that the pkg-installer
uses to determine dependancies, install locations and show a
nice face to the user. The second is the actual file mappings
that are used by fs-pkg to viturtualize the file system.
We have documented the format internally, and this document
will hopefully be flowing to the outside world Real Soon Now.
There is a package builder tool which is in progress which
will make this process much less tedious, maybe a gift for
There should be a QDN article coming out, as soon as I get a
moment to pen it, which goes into a little bit more detail
on how to set up and operate the package filesystem …
and the relationship with the pkg-installer.
If you have specific questions feel free to drop me a line
and I’ll do what I can to help you out.
: Thomas Fletcher wrote:
:> Not yet.
:> Just in case anyone was interested and/or stuck. Installing
:> packages is relatively easy to do by hand. What you won’t
:> get is all of the dependancy auto pick up stuff for you.
:> In any case let’s say you got a package … oh I don’t
:> know maybe abisuite-0.7.x-160800.qpk. Now you need to
:> choose a repository location where you are going to
:> unpack your files to. By default I believe that we will
:> install packages to the user’s local repository which
:> is /pkgs/repository. Unpacking this archive should
:> give you a directory structure that looks something
:> like /[sub-components/…/]. In this
:> case abisuite/abiword.
:> At this point the package installer utility will take
:> a look and see if there are any pre-install scripts
:> to run and run them. We assume nothing, but if you
:> look in the .qpm file that corresponds to the .qpk,
:> or if you look in the MANIFEST file for the package
:> that you just unpacked you should see some entries
:> there for running set-up programs.
:> Once this software is unpacked on your system you
:> need to indicate that you want to actually use the
:> software. You do this by modifing the node configuration
:> file in /etc/system/package/packages (generally).
:> If you have created a new repository you will
:> add that directory to the QPF:repositories
:> section, then add your file to the QPF:packages
:> Tell the package filesystem to re-read the configuration
:> file and you are done.
:> pkgctl -r /dev/pkginfo*
:> Obviously the package installer makes this much more
:> pleasant and incorporates additional features, but
:> if you are really stuck, you can still do things
:> by hand. Hopefully in the near future we will be
:> providing a nice command line utility to do some
:> of this management.
:> : Steve Tomkins wrote in message <email@example.com>…
:> :>Stefan Parvu <firstname.lastname@example.org> wrote:
:> :>: Couple of things:
:> :>: 1. qpk is a standard package format in QNX0? Anyway is good that it is
:> :>: just an standard tgz file for all of use which does not use Photon.
:> :>As long it’s not encrypted.
:> :>: 2. On the other hand what is the way to apply a patch to the system ?
:> :>: patch utility ?..
:> :>Yes, but it’s a GUI app.
:> :>: 3. There are some plans building a boot manager in RTP?
:> :>There already is one. It is optionally installed with the
:> :>partition install.
:> :>: 4. Mans page for System utils, intro info package should be also
:> :>: installed.
:> :>There is a package for man which can be installed. I don’t
:> :>know which utilities have man pages, but most QNX utilities
:> :>will provide usage if you type:
:> :>: Just some ideas ? I can help with any of them.
:> :>: stef
:> :>: Stefan Parvu wrote:
:> :>:> Hello,
:> :>:> Can somebody explain me how can I add packages without GUI Photon in RTP
:> :>:> ?
:> :>:> I think it should be a way to add whatever packages what I need with no
:> :>:> GUI.
:> :>:> RTP Being modular we must not care about GUI at all and I think should
:> :>:> be a way to do it ?
:> :>:> stefan
:> Thomas (toe-mah) Fletcher QNX Software Systems
:> email@example.com Neutrino Development Group
:> (613)-591-0931 http://www.qnx.com/~thomasf
Thomas (toe-mah) Fletcher QNX Software Systems
firstname.lastname@example.org Neutrino Development Group