Occasionally I make a NetBSD source package; but no matter what I did I couldn't satisfy the main collection managers (we don't care if it works as it is, go make it use buildlinks), so I don't even try. I put 'em here, and if someone finds 'em, great.

You use these entirely at your own risk!

Rummage in apps.kde for other descriptions.

*Note, re PMX: I'm not sure g77 compiled mine correctly. When trying to enter Boëllmann's Menuet Gothique, I reached a point where adding staccatos somehow forced a middle system onto its own page, and adding one more staccato causes a coredump.

csh/tcsh/KDE tip

I have my csh/tcsh prompt rigged to set the konsole titlebar to the hostname. The top of my /etc/csh.cshrc:
if $?tcsh then
	set prompt="%{\033]0;`hostname -s`\007%}`hostname -s`: "
else
	set prompt="^[]0;`hostname -s`^G`hostname -s`: "
endif
(^[ and ^G are ESC and BEL resp. Yes, there are probably issues in having it system-wide…and it needs xterm detection.)

Package dependancies

I wrote a tclsh script that lists package dependancies as pairs. Requires a local copy of pkgsrc tree; change one line near the top of the file to point to it. Example: 

> pkgdep x11/kde3 | tsort
x11/kde3
net/kdenetwork3
misc/kdeadmin3
misc/kdeutils3
games/kdegames3
games/kdetoys3
misc/kdepim3
audio/kdemultimedia3
graphics/kdegraphics3
misc/kdeedu3
misc/kdeaddons3
misc/kdeartwork3
comms/pilot-link-libs
databases/gdbm
converters/uulib
x11/kdebase3
graphics/xanim
graphics/imlib
print/ghostscript-gnu
graphics/netpbm
databases/openldap
x11/kdelibs3
fonts/ghostscript-fonts
x11/gtk
graphics/libungif
devel/gettext-lib
graphics/tiff
archivers/bzip2
textproc/libxslt
security/openssl
devel/pcre
audio/arts
audio/libaudiofile
x11/qt3-libs
devel/glib
lang/perl5
textproc/libxml2
devel/pth
graphics/freetype2
graphics/png
graphics/mng
graphics/glut
graphics/glu
graphics/MesaLib
graphics/jpeg
converters/libiconv
graphics/lcms
>

If you installed the packages from the bottom up there'd be no recursive installs needed. (Originally pkg_add would only recurse one level and the dependancies were listed alphabetically instead of topologically. This may have been fixed.) My script doesn't yet list build dependencies, so there can still be some recursion there. (I prefer to make as myself and then make package as root, and sometimes set up builds to run overnight. The easiest way is to arrange to have the appearance of work/.build_done trigger make package (as root) and work/.install_done trigger make for the next package. To prevent a stall on a recursive build, waiting for a root password that won't come, I must chain the latter triggers in complete ascending build dependancy. Which is why I wrote the script in the first place—although it's still not perfect for it.)


created 2003 Mar 8
last update 2003 Jul 15 1