Re: Where to gtkrc-type files go?
> "Marcelo" == Marcelo E Magallon <[EMAIL PROTECTED]> writes: Marcelo> /etc/something.gtkrc (or something like that) or Marcelo> /usr/share/something/something.gtkrc (OSLT) They're not exactly config files -- they're not meant to be changed. But since gtkrc files have no global repository, it's up to you. Personally, I'd use /usr/doc/package/examples/ -- since the gtkrc is meant to be copied to your home directory and edited. -- Brought to you by the letters D and I and the number 1. "Ha ha! I have evaded you with the aid of these pasty white mints!" Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Creating two packages from one source
> "Peter" == Peter S Galbraith <[EMAIL PROTECTED]> writes: Peter> Can a single rules files be used to make two binary Peter> packages from one orig.tar.gz. Sure! Take a look at the debian/rules file from the 'gimp' package -- you can fetch the .orig.tar.gz, .dsc, and .diff.gz from debian/dists/stable/main/source/gimp_1.0.0* on any Debian mirror. You can then extract the source and apply the .diff.gz with the following command: dpkg-source -x gimp_1.0.0-1.dsc Poke around in the gimp-1.0.0/debian/ directory, and read the rules file in there. The gimp package creates a whole bunch of packages. Ben -- Brought to you by the letters V and C and the number 17. "Step away from the car. This car is protected by Viper." -- TMBG Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: Where to put non-end-user binaries?
> "Florian" == Florian Hinzmann <[EMAIL PROTECTED]> writes: Florian> Hi! Lets say a debian package foo contains a binary Florian> "prog" which needs another binary or shell script Florian> "helper" to run. Florian> Should I install these files as /usr/bin/prog and Florian> /usr/lib/foo/helper ? It depends. For my Nethack package, I have a helper/wrapper script in /usr/games/nethack, but the actual nethack executable lives in /usr/lib/games/nethack/nethack. If you intend the end user to run helper, put it in /usr/bin. If you intend them to run prog, put it in /usr/bin. -- Brought to you by the letters T and A and the number 4. "Gorilla Gorilla Gorilla Gorilla Gorilla Gorilla (Stop That)" -- Alliances Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: wmakerconf in slink
> "Marcelo" == Marcelo E Magallon <[EMAIL PROTECTED]> writes: Enrico> Hi, I DL'ed gnome and wmaker (and related libs) and Enrico> wmakerconf and iinstalled them yesterday...I have to say Enrico> you that there is a problem in wmakerconf Enrico> andwmakerconf-data packages: the are both dependent. Here Enrico> is what Packages says: Marcelo> And how is this a problem? Marcelo> wmakerconf doesn't have datafiles of its own, it needs Marcelo> wmakerconf-data. wmakerconf-data won't do anything Marcelo> without wmakerconf installed. They are splitted because Marcelo> wmakerconf-data changes more ofter than wmakerconf. Marcelo> What should I do? Make wmakerconf recommend Marcelo> wmakerconf-data and wmakerconf-data requiere wmakerconf? I ran into this with gimp and gimp-data. I'd do just the opposite of what you said; wmakerconf should depend on wmakerconf-data, but wmakerconf-data should just recommend wmakerconf. I know it's rather silly, but people installing things without apt or dselect can't ever seem to figure out that dpkg -i wmakerconf.deb wmakerconf-data.deb will work. Ben -- Brought to you by the letters G and V and the number 4. "More testicles means more iron." -- Lunchlady Doris, The Simpsons Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: *.m4 files in -dev packages
> "Brian" == Brian Almeida <[EMAIL PROTECTED]> writes: Shaya> I think that is only an issue w/ CVS compilers. If so, not Shaya> your problem. You should NOT be shipping a imlib.m4 in Shaya> your package. Ask the powers that be about this. I could Shaya> be wrong. But this should only affect people who compile Shaya> apps from CVS. and if they are doing that, then they Shaya> should not be using your package anyway. Brian> Are *.m4 files usually distributed in -dev packages, or are Brian> they only needed for those who compile CVS apps? You must distribute the m4 autoconf macros in the -dev package if anyone wishes to create their own autoconf-using program that needs imlib. Ben -- Brought to you by the letters U and Z and the number 6. "My sister has three.. gender biases." -- Moxy Fruvous Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: Checking if directory is empty in postrm
> "Marcus" == Marcus Brinkmann <[EMAIL PROTECTED]> writes: Marcus> can someone give me a hint how I can efficient test if a Marcus> certain directory is empty in the postrm (shell script)? Here's what I did in the /etc/rc.boot/nethack script: # Are there any lock-files to recover? ls /var/lib/games/nethack/*lock.0 >/dev/null 2>&1 || exit 0 You can obviously replace the *lock.0 with * if you want to see if it's completely empty. -- Brought to you by the letters O and P and the number 16. "Hello! We are only joke. It is funny enough." -- Orz, SCII Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
New unstable GTK+/GLib packages' names -- seeking advice
GTK+ and GLib have a somewhat curious developmental situation; they release versions that are binary (and source, sometimes) incompatible with previous releases with each developmental 1.1.x release. Version 1.1.5 of both GTK+ and GLib have just been released. I have received complaints about packages compiled against, say GTK+ 1.1.2, breaking as soon as 1.1.3 is installed. Should I: 1) make the source and binary names for the new packages like gtk+1.1.5 and glib1.1.5, changing the source and binary package names each time a new developmental upstream release comes out or 2) say "screw it" and make the shlibs for GTK+ and GLib be (=1.1.5-1), updating the exact dependancy each time a new package is released. 1) lets there be packages that depend on any gtk+/glib version stay in the archives, but takes up about 3-4 times as much space on every mirror as before 2) makes it so that if you want something compiled against GTK+ 1.1.5 installed on your system, you'll have to remove all other packages that don't depend on the exact version from your system. But, there aren't 5 million GTK+/GLib packages in the archives. Which should I do? Ben -- Brought to you by the letters M and B and the number 14. "You have my pills!" -- Grampa Simpson Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: New unstable GTK+/GLib packages' names -- seeking advice
> "James" == James Troup <[EMAIL PROTECTED]> writes: James> dpkg doesn't do reverse dependency checking[1]; if I have James> say foo installed which depends on libgtk1.1 (= 1.1.5-1), James> it'll happily let me install libgtk1.1 1.1.6-1, silently James> breaking foo. James> (1) is the only option. If we limit the number of packages James> compiled with gtk1.1 (as opposed to gtk1), it won't be that James> big a deal, IMHO. (Space is not an issue, if it were, we James> would presumably get rid of iraf, picons, timidity patches James> or something similar first). Okay. I will release gtk+1.1.5 and glib1.1.5 source/binary packages soon. What should I do about the old gtk+1.1 and glib source packages whose names don't match the new setup? Should they be removed from the archives as soon as no more packages are dependant upon them? Ben -- Brought to you by the letters M and B and the number 19. "Nerd. Loser. Jerk. Moron. Worm. Scum. Idiot. Fool." -- Pkunk, SCII Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: What to do with extra sources needed to build a package
> "Peter" == Peter S Galbraith <[EMAIL PROTECTED]> writes: Peter> I'm in the process of packaging xplot (a simple data Peter> plotter for X. It's designed to show one- or twodimensional Peter> datasets, either from a file or from a pipe). It uses Peter> XForms, which put it in contrib. Peter> To build it, I must also install an extension to XForms Peter> called libfli. The program is statically linked against Peter> libfli, such that libfli is not required to use xplot. Peter> What should I do about libfli? *snip* Peter> 3- Package libfli also? It appears to have extensions Peter> useful to XForms developers. This is the right thing to do, assuming we can redistribute libfli. Make packages for libfli2 and libfli-dev (assuming the soname of libfli is 2, for example) and you'll be set. Do you have experience building Debian packages of libraries? There are a few gotchas that you'll hit if you don't have experience in it already. Ben -- Brought to you by the letters D and X and the number 0. "Hello! We are only joke. It is funny enough." -- Orz, SCII Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: What to do with extra sources needed to build a package
> "Ionutz" == Ionutz Borcoman <[EMAIL PROTECTED]> writes: Ionutz> Can you please give some examples about these 'gotchas' ? Ionutz> I also want to pack some shared libs. Learning how to make shlibs files properly, how to decide what the dependancies between the -dev and library package will be (versioned? not versioned?) and when to run ldconfig in the postinst script and when not to run ldconfig are a few of them. -- Brought to you by the letters A and R and the number 5. "Do you wish to see our *surprising toys*? No! Do not!" -- Orz, SCII Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: Packaging beyond one's means
> "Jason" == Jason Henry Parker <[EMAIL PROTECTED]> writes: Jason> I checked on master and va, they only have GTK1.0 Jason> installed, not GTK1.1, which mozilla needs to build. Are Jason> there any hosts offered by debian that have libs from Jason> unstable to help out in this sort of situation, or should I Jason> let someone else carry the flame for a Debianised mozilla? potato has the newest GTK+ 1.1. /debian/dists/unstable/main/binary-i386/libs/libgtk1.1.6_1.1.6-1_i386.deb Ben -- Brought to you by the letters D and B and the number 16. "He's kissing Christian.. and it's making you die." -- that dog. Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: problem with ldconfig and packaging libs
> "Ionutz" == Ionutz Borcoman <[EMAIL PROTECTED]> writes: Ionutz> Hi, I am trying to package my first set of libs. I am Ionutz> doing this from my account with fakeroot. The problem is Ionutz> that this way, the process stops with the following error: (ldconfig not found) Have you tried putting /sbin in your PATH environment variable? -- Brought to you by the letters G and Y and the number 5. "You have my pills!" -- Grampa Simpson Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: automatic dependencies question
> "Ionutz" == Ionutz Borcoman <[EMAIL PROTECTED]> writes: Ionutz> Hi, I am trying to package VDK libs. I have added this in Ionutz> my control file: Ionutz> libvdk depends on libgtk 1.1.7 or more. However, this is Ionutz> what I get in my libvdk1.deb: Ionutz> No reference to libgtk or libglib at all. What am I doing Ionutz> wrong ? Did you install your own libgtk without using packages? The only way dpkg-shlibdeps (the package that figures out the shared library dependancies) can know how to set up a shared library dependancy is if a file /var/lib/dpkg/info/*.shlibs exists that defines a dependancy for libgtk. Since there are no gtk+ 1.1.7 .debs out yet (1.1.9 .debs are building right now) I'll assume you installed your own, and thus you don't have a shlibs file for 1.1.7 in /var/lib/dpkg/info/, as there is no package for them to depend on. :) Please wait until I release 1.1.9 .debs. Ben -- Brought to you by the letters M and G and the number 0. "If you turn both processors off, you will have to reboot." -- The Be Book Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: automatic dependencies question
> "Ionutz" == Ionutz Borcoman <[EMAIL PROTECTED]> writes: Ben> Did you install your own libgtk without using packages? The Ben> only way dpkg-shlibdeps (the package that figures out the Ben> shared library dependancies) can know how to set up a shared Ben> library dependancy is if a file /var/lib/dpkg/info/*.shlibs Ben> exists that defines a dependancy for libgtk. Ionutz> I have installed using the debs created from CVS. Another Ionutz> program I am packing (my first attempt to pack anything, Ionutz> by the way, links against libgtk and libvdk) reports Ionutz> corectly the dependencies. Here is what langdrill reports: You really oughtn't to build packages using packages outside of Debian :) Ionutz> Glad to hear that 1.1.9 are on the way. As I have pointed Ionutz> out, it seems that I'm doing something else wrong. I will Ionutz> wait anyhow for 1.1.9 and see if the problem is still Ionutz> there. (By the way, I have used the scripts from libglib Ionutz> 1.1.3 as a guide in creating my own rule file for Ionutz> libvdk1). 1.1.9 GLib and GTK+ packages are in Incoming. I'm glad I could help you with libvdk1 :) -- Brought to you by the letters O and N and the number 4. "More testicles means more iron." -- Lunchlady Doris, The Simpsons Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: problem with ldconfig and packaging libs
> "Adam" == Adam Di Carlo <[EMAIL PROTECTED]> writes: Adam> No, you just need to be careful and to read the Packaging Adam> Manual, where it says: Adam> Any package installing shared libraries in a directory Adam> that's listed in `/etc/ld.so.conf' or in one of the default Adam> library directories of ld.so (currently, these are Adam> `/usr/lib' and `/lib') must call ldconfig in its postinst Adam> script if and only if the first argument is Adam> `configure'. Hoo boy.. didn't we end up deciding this was wrong? -- Brought to you by the letters I and G and the number 18. "He's kissing Christian.. and it's making you die." -- that dog. Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: problem with ldconfig and packaging libs
> "Ionutz" == Ionutz Borcoman <[EMAIL PROTECTED]> writes: Adam> This whole thread is absurd since the question was about Adam> someone running ldconfig in debian/rules, which is a big Adam> nasty no-no as well, and I can't think of a possible reason Adam> why it would be necessary. Ionutz> The ldconfig was run by the "make install" of the original Ionutz> source package. To make the links to the library. Ionutz> ldconfig $(LIBS) This is wrong. You should make the links yourself in debian/rules, since the make install is running ldconfig. So, copy the libblah.so.1.2.3 in debian/rules to debian/tmp/usr/lib/ then ln -s libblah.so.1.2.3 debian/tmp/usr/lib/libblah.so.1 . Then, in the libblah-dev target of debian/rules, you should ln -s libblah.so.1.2.3 debian/libblah-dev/usr/lib/libblah.so . Ben -- Brought to you by the letters M and T and the number 9. "Johnny! Don't go! It's too dangerous!" "I don't care!" -- MST3K Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: problem with ldconfig and packaging libs
> "James" == James Troup <[EMAIL PROTECTED]> writes: Ben> Hoo boy.. didn't we end up deciding this was wrong? James> Eh? No, we certainly did not. I'm pretty sure it's safe to call ldconfig unconditionally in postinst, and that we ran into problems when we literally followed the packaging manual. -- Brought to you by the letters M and B and the number 3. "Gorilla Gorilla Gorilla Gorilla Gorilla Gorilla (Stop That)" -- Alliances Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: library packaging howto?
> "Will" == Will Lowe <[EMAIL PROTECTED]> writes:
Will> I've been around for a while, I have a couple of packages.
Will> I'm about to undertake packaging my first set of libraries,
Will> and I'm not sure what's different. I understand that a
Will> stripped copy of the library goes into the {package}lib.deb,
Will> and that a debugging-enabled copy (and header files) go into
Will> {package}lib-dev.deb, but what else do I need to do?
Pretty much it's a matter of looking at an existing package -- that's
how you learn.
Take a peek at bash's debian/rules file to see how it does
libreadline, or look at libgtk1's debian/* files to see how a pure
library package is handled.
The short is:
.so.1 and .so.1.0.0 go into libblah1
.so and .a and .h files go into libblah-dev
(optional) debugging-enabled .a goes into libblah-dbg
Your numbers may vary.
--
Brought to you by the letters N and I and the number 11.
"Ha ha! I have evaded you with the aid of these pasty white mints!"
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet/Open Projects IRC as Che_Fox.
Re: library packaging howto?
> "Josip" == Josip Rodin <[EMAIL PROTECTED]> writes: Ben> The short is: Ben> Ben> .so.1 and .so.1.0.0 go into libblah1 .so and .a and .h files Ben> go into libblah-dev (optional) debugging-enabled .a goes into Ben> libblah-dbg Ben> Ben> Your numbers may vary. Josip> I think I saw somewhere a library that did not have Josip> libblah.so as an actual file, but a symlink to Josip> libblah.1.0.0 (which was a file, of course :) Is it Josip> possible, and what to do then? Ack! I'm sorry. Only the .so.1.0.0 file will be an actual file. The .so.1 and .so files *will* be symlinks. Josip> Also, libblah1 goes to libs section, and -dev and -dbg into Josip> devel section, right? If so, libfltk-dev is misplaced. Josip> FWIW I'd like -devs in libs section. There isn't policy (unfortunately) but yes, that's the accepted standard. -- Brought to you by the letters W and J and the number 16. "It is sad. *Campers* cannot *dance*. Not even a *party*." Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet/Open Projects IRC as Che_Fox.
Re: What to do?
> "Mitch" == Mitch Blevins <[EMAIL PROTECTED]> writes: Mitch> I believe that the technical term for what I've done is a Mitch> 'boo-boo'. I blame it on raging stupidity on my part. But Mitch> how can I fix it? Mitch> Here's the situation: Mitch> I uploaded gtksamba-0.1.4 -- no problem. I uploaded Mitch> gtksamba-0.3.0 -- no problem. I uploaded gtksamba-3.1 -- Mitch> PROBLEM! Mitch> As you can see, I left out the '0.' on the front of the Mitch> revision. This is what epochs were meant for. In your debian/changelog, make the next revision 1:0.3.2 and all will be fine. You will just need to make sure to use the 1: prefix from now on whenever referring to the version, in Dependancies or whatnot. -- Brought to you by the letters C and N and the number 15. "Moshimoshi. Kikoemasu ka?" "Kakenaoshimasu kara ne! 1-do kitte kudasai." Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet/Open Projects IRC as Che_Fox.
SGML-format docs -- compile-time, what to do?
I'm making a new libgtk-doc package. Included with the upstream source is a SGML-formatted GTK FAQ. Should I: 1) convert the SGML to HTML/LaTeX/??? at compile time 2) convert the SGML to HTML/LaTeX/??? in the postinst 3) forget this silliness? :) And if I do convert the SGML to whatever, how should I go about doing that the best way? Ben -- Brought to you by the letters E and A and the number 19. "Johnny! Don't go! It's too dangerous!" "I don't care!" -- MST3K Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Packages getting absorbed by other packages..
Hey, folks. I maintain the GIMP set of packages, which until version 0.99.18 consisted of a main gimp package, a required gimp-data-min package (with separate source) and other sundry packages. The upstream 0.99.19 version has absorbed the gimp-data-min package into the main gimp source. To accomodate this, I added gimp-data-min to the Conflicts:, Replaces:, and Provides: lines in debian/control: Package: gimp Architecture: any Section: graphics Conflicts: gimp-smotif, gimp-dmotif, gimp099, gimp-data-min Replaces: gimp-smotif, gimp-dmotif, gimp099, gimp-data-min Provides: gimp-data-min but dpkg will not install the resultant gimp package without --auto-deconfigure specified to let it deconfigure the old gimp and remove the old gimp-data-min and then install the new gimp. Am I doing something wrong, or is --auto-deconfigure going to be required here? Ben -- Brought to you by the letters A and R and the number 13. "I'm calling from the plane. I'll call you when I get there." -- TMBG Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Re: One source, two binary packages
@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false binary: binary-indep binary-arch .PHONY: build clean binary-indep binary-arch binary -- Brought to you by the letters M and S and the number 11. "Gorilla Gorilla Gorilla Gorilla Gorilla Gorilla (Stop That)" -- Alliances Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: One source, two binary packages
>>>>> "Santiago" == Santiago Vila <[EMAIL PROTECTED]> writes: Santiago> I disagree here. Santiago> If you put this in a different debian/rules target Santiago> (called, for example, automake-refresh), then you and Santiago> only you would be forced to have automake and autoconf Santiago> installed, but nobody else. That's why the comment said that it's unnecessary for that package. For the GIMP packages, it is required; they ship with a libtool that is incompatible with Debian policy. I have to run automake/aclocal/autoconf every single time the package builds to remove all vestiges of the old libtool and replace it with the Debian libtool. -- Brought to you by the letters C and Y and the number 17. "I put my feet on the Ottoman.. Empire." -- Moxy Fruvous Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: One source, two binary packages
>>>>> "Scott" == Scott Ellis <[EMAIL PROTECTED]> writes: Scott> You actually only need to run it once. Once they've been Scott> run once (probably right after porting your changes into a Scott> new version), the updated files are left behind and will be Scott> included in the diff generated when you build the package. In my experience, making the diff file huge makes porting and new versions unnecessarily difficult. The only way I've been able to keep my sanity with the plethora of GIMP/GTK+ releases is this solution. -- Brought to you by the letters B and V and the number 6. "Do you wish to see our *surprising toys*? No! Do not!" -- Orz, SCII Ben Gertzfield <http://www.imsa.edu/~wilwonka/> Finger me for my public PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
