I'd be willing to install X-Chat from the source tarball, it's just that
a source tarball doesn't exist. And applying the patches manually is
just a little too much.
I'm looking forward to faster and more secure DCC, though, so I hope all
the patches get implemented for the next version.
-Dave
--
XChat-discuss: mailing list for XChat users
Archive: http://mail.nl.linux.org/xchat-discuss/
What I meant is that Gentoo should do like FreeBSD does, and add that
patch to their tree, so whoever updates/install xchat gets those
patches.
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
Speaking as one of the maintainers of this pack for Gentoo, we had the
security bugfix patch in probably before any other distro (we did our
own). The other fixes are minor, not 'official' (the aren't listed in
the patches dir), have not been requested and so have no immediate
priority to us. Peter sort of said there would probably be another
release soon-ish, with the real nagging problem solved i see no direct
reason to add the secondary patches right now. Certainly not as long as
there has been no official request via our bugzilla, there are more
important matters that need our attention first.
Anyway its a 2 line change to include the other 2 patches in a local
only ebuild and have the full patched version local (check out the
portage overlay possibilities for a nice clean way to do this). No need
for messing around with tarballs if the patches apply cleanly (which i
assume they do).
- foser
Gentoo GNOME developer
I suppose so, but I have a potentially good idea.
Have those two patches been implemented in CVS yet? If so, I could just
use the CVS source in portage and forget about the whole thing until
2.0.7 is released.
-Dave Oftedal