Note to anyone creating packages using packager (as if there is any other
way to do it)…
When packager creates my packages, the first thing I check is the list
of packages that are created. Quite often, packager creates more packages
than are required for a simple product. For instance, if I have .h or .a
files, packager will create separate Development packages to house these
files which are obviously for development purposes only. This is a great
feature, don’t you think? Yes-however, if the product that I’m packaging is
inherently a development utility, separating the files into development and
non-development packages adds extra complexity which is not needed.
The question you have to ask yourself is whether you want the user to be
able to install just the executable portion, or to install just the
development portion, without the other packages. If the answer is yes, then
packager has done all the work for you and life is good. However, if there’s
no need for users to have this granularity, you should tell packager to not
create separate development packages at all; the files will be merged into
the other packages automatically. To achieve this, you can do one of two
things:
(1) Run packager with the -D option on the command-line.
(2) Edit your QPG file so that development packages are never created.
Do this by adding dev=“no” to the FileSorting line in your QPG:Options
block, like this:
QPG:Generation
QPG:Options
<QPG:FileSorting dev=“no”/>
</QPG:Options>
</QPG:Generation>
The generated packages will no longer have the dev- portion of their name.
Many thanks.
Jerry Chappell
“Dave Rempel” <drempel@qnx.com> wrote in message
news:3DD13D88.7000102@qnx.com…
Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later > 
> . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
I’ve already done a scan of the various projects out there as well and
looked to see what needs to be updated and created a list of what we
would like to do. I’ve attached this list to this posting.
What I’m looking for is a few things:
- Eyes to go over this list and make any corrections (as well as fill
me in on what needs to be done on the things that don’t have anything
beside them…ie: is there a New cogent package to go out?)
- New content that exists out there already for QNX that I have missed
- Suggestions for new content that may not already exist but will
likely prove to be an easy port.
- New projects that are currently being developed that will likely be
ready in time for this cd’s release (and the author wishes it to appear
here).
- Volunteers to help with the porting/packaging effort.
- Any other suggestions as to what could make this cd better.
For those of you that don’t know already, the 3rd party CD is an
unsupported cd that QSSL distributes, and is a volunteer based project.
Not everything on this list may make it to the CD. It will depend
entirely on the number of people working on it and the amount of time we
have. Right now I’m looking at the middle of January (17th?) as the
cut-off date for new content to be submitted. We’ll be testing the
various packages before then, but I think we’ll need at least a couple
of weeks to test the final distribution, fix any bugs that we can, and
pull stuff that doesn’t work and we aren’t going to be able to fix.
Please respond here in this news group.
Thanks for you time.
Dave Rempel
Status:
N = New
U = Needs Update (new stable/release version has been released)
C = In unsupported CVS tree
P = In a Package
x = Version on the previous 3rd party cd is to be used
B = Needs bug fix update (bugs specific to the QNX port/package only)
D = Done (it’s in the 3rd party cd repository and there are no known
issues)
Source:
x = Source code is available, it is legal to put it on the cd, and we
intend to do so.
D = Source tarball is on the unsupported cd’s filesystem
– blank on status means unknown
Title Status Source
AbuseDemo CPx
CascConnect
CascDataHub
CascHist
CascTextLog
CogentAPI
GNUEmacs
Gamma
GammaGTK
JFSolitaire CPx
KiPhoton
PGLib U
PhAlarm
PhCam
Phumb
a2ps CPx x
alienwave UC x
allegro audio driver x
alsa_utils CPx x
apache1 x
autoconf U x
automake U x
bash U x
bitchx U x
blackbox U x
centericq U x
cpio U x
ctags UC x
curl U x
db U x
ddd U x
dia U x
doxygen U x
elib x
fetchmail U x
fvwm U x
gaim U x
gcal B x
gdbm U x
gdk U x
gettext U x
gimp B x
glib U x
gnuchess CPx x
gnudiff U x
gnugo CPx x
gnutextutils U x
groff U x
gtk U x
indent CPx x
ipaq_columns CPx
ipfbin U x
ircii U x
jed U x
jikes U x
lesstif U x
libIDL CPx x
libart U x
libaudiofile Px x
libiconv U x
libmikmod U x
libpng U x
libsigc++ U x
libtiff U x
libtool U x
libxml2 U x
links U x
lopan CPx x
lynx CPx x
m4 CPx x
maestro audio driver x
mailplugin U
man U
mkdepend CPx x
mpg123 – licensing issues with new patent treatment?
mqc
mutt U x
nail U x
nano CPx x
ncftp U x
ncurses U x
openldap U x
openssh U x
openssl U x
patch CPx x
pcl
perl UC x
phPostal
phSambaChat
phViewer
Abiword (Photon version) U x
ph_ipaqxmp
phaster
phdiff
phftp
phhotkey
phirc
phmame x
phmine_02
photon3d CPx
pine U x
pkgconfig x
pkiphoton
pocket_phumb
postgresql U x
psgml
pureftpd U x
python U x
readline U x
rogue CPx x
rsync CPx x
ruby CPx x
samba U x
screen CPx x
seatris CPx x
sendmail U x
snes9x CPx x
soundtracker Px x
spin
stow
t1lib U x
tcpdump U x
tin U x
tspc
uuencdec CPx x
vim U x
wget U x
workspace U
xchat U x
xfree86 x
xpdf U x
zebra U x
zsh U x
libungif N x
freeciv N x
libSDL N x
libSDL-mixer N x
libSDL-image N x
lbreakout N x
maelstrom SDL N x
liballegro N x
tetris queen (Allegro) N x
bluefish N x
euler N x
distributed net client N x
PhNetLoad N
FreePascal N x
PhAmp N
figlet NC x
figlet contributed fonts NC NA
Bochs N x
mkisofs N x
elm N x
uae (SDL) N x
c-scope N x
nedit N x
aview N
phchess N x
