Re: Misc questions: add image to package, man page for cgi script, etc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Frédéric,
On Mon, Nov 25, 2002 at 11:35:26PM +1100, Frederic Schutz wrote:
> 1) I'd like to add a binary file to the upstream source (an image, so that
> all images are available locally and no Internet connection is needed).
> Obviously, the diff file doesn't like binaries, so what is the best way to
> do it ? [Currently, I added the image as a uuencoded file, with a
> "Build-Depends: sharutils" (sharutils contains uudecode) and a line in
> debian/rules that decodes it at build time]
You have to use uuencode/uudecode. There is also a Perl script for this.
This should answer your question:
http://lists.debian.org/debian-mentors/2002/debian-mentors-200203/msg00027.html
IIRC, theres development to enable binary diffs for the debian package utils,
but I dont remember the thread anymore.
> 2) Should I write a man page for a CGI script ? If yes, could someone
> point me to an example of such a page ?
No, there is no rule that one must have a man page for CGI scripts.
Usually I make a note in the package description, in README or in
README.Debian (whatever seems appropriate) that theres a CGI script available.
> 3) The package contains a Perl script that can be used either as a cgi-bin
> and on the command line [it is not the same script than in 2) and I
> already wrote a man page for the command line version]. I can install it
> in either /usr/lib/cgi-bin or /usr/bin and put a symbolic link in the
> other directory. What is the best way to do it ? I would think that I
> should put it in the cgi-bin directory, since the web server (Apache) will
> probably not follow a symlink, while this is not a problem for a command.
> Any other thought on the question ?
As you said, you should not have symlinks pointing outside of
/usr/lib/cgi-bin. I think there are two options:
a) symlink from /usr/bin/foo to /usr/lib/cgi-bin/foo
b) Make a cgi-only version and a commandline-only version of the script
and put them in the proper dir.
Because I'm lazy, I'd prefer a).
Cheers, Bastian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE94iXceBwlBDLsbz4RAjEOAKC1pFcMFhj+Pvag8tRHYKEgbagssQCeNh2s
YaxPrleHItp/r6AuDx2F+nk=
=gu+8
-----END PGP SIGNATURE-----
Reply to: