JAMlib is a collection of subroutines that encapsulate much of the format-specific and tedious details of the JAM message base format. By using these routines, application programmers can concentrate on the higher-level issues of their programs instead of worrying about their JAM routines.
libDockApp is a simple library for easily writing Window Maker dock applications, also known as dockapps (those that only show up in the dock). It is very limited and can only be used for dockapps that open a single appicon for each process in only a single display, but this seems to be enough for most, if not all, dockapps.
Re: The obvious solution.....
> ... is to have developers build their
> own packages, which are the official way
> to install the software. The team that
> wrote the software are the best
> qualified to package it anyway.
I can't agree with you. All distributions have their little differences (well, some of them are little, some are not), and software developer must mention all this differences. For example, packaging policy (menu groups, documentation placement, package nameing, in case of RPM - various distribution-specific specfile macros), security issues (PAM modules, control(8) like in Owl and ALT). And developer still must do further development...
Developer is qualified to develop software and packager is qualified to package this software for his distribution.
JAMlib on SF.net
I have started JAMlib project on SourceForge. http://sourceforge.net/projects/jamlib/