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
Stefan Parvu <stefan.parvu@comptel.com> 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 ?
The package installer is a GUI application so you need to run
the GUI to install packages.
: stefan
This is vital … belive me if photon is down you can’t do almost
anything.
And on the other hand:
We need an command line tool for installing the stuff. There are users
which does not need GUI!
Documentation could be as well non GUI. use is a bit poor. We need
pages good documented. I can help here if needed.
I am planning to install fuzz black box testing tool for testing every
bins file from RTP.
Please let me know if you have some kind of beta stage of this tool to
install … I really need it.
Stefan
Steve Tomkins wrote:
Stefan Parvu <> stefan.parvu@comptel.com> > 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 ?The package installer is a GUI application so you need to run
the GUI to install packages.: stefan
“Stefan Parvu” <stefan.parvu@comptel.com> a écrit dans le message news:
39D1B3C7.DEBF175F@comptel.com…
Hello,
Can somebody explain me how can I add packages without GUI Photon in RTP
?
well, the .qpk files are simply .tar.gz files you can uncompress and untar
after renamed…
files are located on QNX web site, for example:
http://packages.qnx.com/repository//binutils-core-2.9.1-x86.qpk
Hi,
Why they are called qpk if they are normal arch ?
Anyway good that exists a way to install them.
On the other hand we need a boot manager !!! Some ideas here ?
Stefan
“Frédéric” wrote:
“Stefan Parvu” <> stefan.parvu@comptel.com> > a écrit dans le message news:
39D1B3C7.DEBF175F@comptel.com> …
Hello,Can somebody explain me how can I add packages without GUI Photon in RTP
?well, the .qpk files are simply .tar.gz files you can uncompress and untar
after renamed…
files are located on QNX web site, for example:
http://packages.qnx.com/repository//binutils-core-2.9.1-x86.qpk
Couple of things:
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.
On the other hand what is the way to apply a patch to the system ?
patch utility ?..
There are some plans building a boot manager in RTP?
Mans page for System utils, intro info package should be also
installed.
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
Stefan Parvu <stefan.parvu@comptel.com> 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:
use
: 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
In QNX 4.2x,
we were used to
/etc/install -u thePackage.tar.F
but I have no clue if this tar/freeze format
is also supported in RtP or tar/gzip (qpk)
is the new format for file release…
Is there any equivalent to /etc/install under RtP ?!?
Fred.
Steve Tomkins wrote in message <8qvqrg$afe$7@nntp.qnx.com>…
Stefan Parvu <> stefan.parvu@comptel.com> > 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:use <command
: 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
Fred <fprog@users.sourceforge.net> wrote:
: In QNX 4.2x,
: we were used to
: /etc/install -u thePackage.tar.F
: but I have no clue if this tar/freeze format
: is also supported in RtP or tar/gzip (qpk)
: is the new format for file release…
: Is there any equivalent to /etc/install under RtP ?!?
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
section.
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.
Thomas (toe-mah) Fletcher QNX Software Systems
thomasf@qnx.com Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf
Hello.
Thanks for the info on the .qpm and .qpk stuff, Thomas.
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
difficult.
Or can the Package manager do this?
Thanks in advance.
Rodney Lott
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
section.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.Thomas
: Steve Tomkins wrote in message <8qvqrg$afe$> 7@nntp.qnx.com> >…
:>Stefan Parvu <> stefan.parvu@comptel.com> > 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:
:
:>use : 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
thomasf@qnx.com > Neutrino Development Group
(613)-591-0931 > http://www.qnx.com/~thomasf
Rodney Lott <rod@fuelcelltechnologies.ca> wrote:
: Hello.
: 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
: difficult.
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
Christmas.
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
: 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
:> section.
:>
:> 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.
:>
:> Thomas
:>
:> : Steve Tomkins wrote in message <8qvqrg$afe$7@nntp.qnx.com>…
:> :>Stefan Parvu <stefan.parvu@comptel.com> 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:
:> :>
:> :>use
:> :>
:> :>
:> :>: 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
:> thomasf@qnx.com Neutrino Development Group
:> (613)-591-0931 http://www.qnx.com/~thomasf
Thomas (toe-mah) Fletcher QNX Software Systems
thomasf@qnx.com Neutrino Development Group
(613)-591-0931 http://www.qnx.com/~thomasf
Thanks, Thomas.
Well, if there will be documents flowing out, then that is good. I am
not in any hurry but am merely curious, so I will wait. If in the event
I need to
do any packaging and am in dire need of help, I will contact you.
I will look forward to what is in store. Thanks for the good work and
keep it up.
Rodney
Thomas Fletcher wrote:
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
Christmas.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
hi,
These are good news. I meant is good that at least without GUI you can
install stuff on RTP.
I think Solaris from this point of view is really ok.
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.
But anyway I think the first step was to provide tools for command line
to add/remove packages and then GUI tools. Administration is an easy
task if you have simple tools to use.
BTW I am curious how many users can I have in the same time in QNX RTP ?
There is a definition somewhere about this ? Or there is a dynamic
support ?
stefan
Rodney Lott wrote:
Thanks, Thomas.
Well, if there will be documents flowing out, then that is good. I am
not in any hurry but am merely curious, so I will wait. If in the event
I need to
do any packaging and am in dire need of help, I will contact you.I will look forward to what is in store. Thanks for the good work and
keep it up.Rodney
Thomas Fletcher wrote:
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
Christmas.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