Subject: Re: Using gcc/g++-3.2 as default compiler - msg#00271

Previous Message by Date: click to view message preview

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-----

Next Message by Date: click to view message preview

new package name for gtk-engines-mgicchikn

hello list.. i am currently adopting the package "gtk-engines-mgicchikn", whereas one task is to rename the package. so i think that "gtk2-engines-magicchicken" is a fine name for it. unfortunately, there are 25 characters necessary for this name. the developer's reference suggests to use no more than 20 characters. but the "mandatory" prefix "gtk2-engines-" alone needs 12 characters, so crippling the name of the theme itself to 8 characters would be necessary to comply with the aforementioned suggestion. how do tools like aptitute, deity, etc. cope with these long names? my sponsor and i agree on "gtk2-engines-magicchicken", despite its length. what do the others think about it? thanks, sebastian -- ::: sebastian henschel ::: kodeaffe ::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import

Previous Message by Thread: click to view message preview

Using gcc/g++-3.2 as default compiler

Hello all, I am trying to build a new version of one of my packages, as upstream has ported it to gcc/g++-3.2 and KDE3. It would be nice to have the kinks ironed out before the transition actually happens in sid, I think. I am wondering if anyone has any good method for switching the default compiler. I am using a pbuilder chroot, and so I log in, and then switch the symlinks (gcc, g++, gcov, and cpp) to point to the 3.2 versions. For now, the build is failing. In order to help sort it out, are there any other links I should be switching? Some other (smarter?) way to do this? It builds fine before I mess with any of the links, or set environment variables (CC, CXX, CPP), so I'm not convinced that it's a code problem, although it may be - I know there are many incompatibilities between the two versions. TIA, -- -------------------------------------------------------------------------- | Stephen Gran | Life is a series of rude awakenings. | | steve@xxxxxxxxxxx | -- R.V. Winkle | | http://www.lobefin.net/~steve | | -------------------------------------------------------------------------- pgpnwaXdU36ZS.pgp Description: PGP signature

Next Message by Thread: click to view message preview

hinfo -- looking for sponsor

I'm looking for a sponsor for my package hinfo. It's at: http://www.blars.org/debian/blars/hinfo/ (source and "binary", passes lintian and linda) Source: hinfo Section: net Priority: optional Maintainer: Blars Blarson <blarson@xxxxxxxxx> Build-Depends-Indep: debhelper (>> 3.0.0) Standards-Version: 3.5.2 Package: hinfo Architecture: all Pre-Depends: adduser, debconf (>= 0.5), userinfo Depends: perl, libnet-dns-perl Recommends: wget Description: deobfuscate addresses, DNSBL lookups, and whois IP checker Hinfo will deobfuscate addresses, perform lookups to a (configurable) variety of DNSBLs such as relays.osirusoft.com and bl.spamcop.net, and display the owner of the IP block the address is in. It is primarily intended as a tool to aid manual spam reporting. -- Blars Blarson blarson@xxxxxxxxx http://www.blars.org/blars.html "Text is a way we cheat time." -- Patrick Nielsen Hayden