Re: Documentation for upstream software authors
-----BEGIN PGP SIGNED MESSAGE-----
Adrian 'Dagurashibanipal' von Bidder wrote:
> I've just started http://wiki.debian.net/SoftwarePackaging, intended to
> collect thoughts of packagers how upstream developers can make the life of
> a packager easier.
> I'm sure all packagers have wondered about "brain-dead" upstream developers
> who have not put much thought into how their software might be distributed
> in a pre-compiled/pre-configured package. Compile-time options are one
> example, user-modifiable files outside of /etc are another, to name the two
> that I could think of just now.
I wrote something vaguely similar after getting frustrated at a number
of problems with free (either as in beer or speech) physics software.
Maybe you can find something useful in it:
In case you need a licensing statement, I hereby license the entire
contents of that HTML file (not including images or CSS) under the BSD
license (found in /usr/share/common-licenses/BSD on a Debian system),
substituting my name for "The Regents of the University of California"
and "the University".
Kevin B. McCarty <firstname.lastname@example.org> Physics Department
WWW: http://www.princeton.edu/~kmccarty/ Princeton University
GPG public key ID: 4F83C751 Princeton, NJ 08544
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----