Gaim 2.0.0 beta1 has been released. It would be nice to see this in portage as a masked or keyworded pkg.
I've modified the 1.5.0 ebuild to use the 2.0.0beta1 package and it is working well on my amd64 machine.
Created attachment 75007 [details] gaim-2.0.0_beta1.ebuild Initial ebuild * Addedd mono, dbus and vv EUSE
It seems to be missing the preferences that control what keys send messages. I like to use ctrl-enter instead of enter.
net-im: now that rizzo is gone? How do you want to handle gaim? There seems to be quite a lot of demand, we could add it package.masked.. (In reply to comment #3) > It seems to be missing the preferences that control what keys send messages. I > like to use ctrl-enter instead of enter. The gaim changelog says you can edit that in the GTK theme (whatever that means). (In reply to comment #2) > Initial ebuild > * Addedd mono, dbus and vv EUSE I'm pretty sure that at least for dbus, it depends on a specific version since the API has changed.
If you do add this I would stress that it is beta, and hold out hope that users can distinguish between actual bugs and stuff like feature changes. I wouldn't want to get a crapload of gentoo bug reports for beta software. PS it seems I still have full developer status. Not sure who to contact about getting out.
You may want to add an additional warning regarding backing up your ~/.gaim directory as suggested by the Gaim devs.
Definitely.
Also that gaim-encryption and gaim-otr do not build with this version as of yet. I think it would be best to leave this bug open and not yet add it to the tree just yet...
I don't think anyone here has suggested it be blindly added into the portage tree. It is beta software. What I would like to see is at least a masked package. This version is able to maintain connections to the various networks 10x better than 1.5.0, and that is much more important to me than plugin support.
I tend to disagree. There is certainly plenty of precedent for putting packages into the tree when plugins don't yet work - it happens with thunderbird/enigmail with every release, and IIRC, it has happened with gaim before. If you followed the approach you suggest, you'd never get it out the door until every plugin author got around to updating. Users can simply mask things/choose not to unmask them if it breaks something they need - that way, everybody gets to be on the good side (as some old Australian fencing advertisement went). On a related note, guifications doesn't build either. Further, think I have already found a significant bug... when using a http proxy, it doesn't seem to send my credentials to the proxy server. I'll investigate a bit further, but it wasn't happening on a cvs cut of gaim I took a couple of weeks ago, so, it may even be gentoo specific.
(In reply to comment #5) >PS it seems I still have full developer status. Not sure who to contact about >getting out. You want to get out but we dont let you :P (In reply to comment #10) > I tend to disagree. There is certainly plenty of precedent for putting > packages into the tree when plugins don't yet work - it happens with > thunderbird/enigmail with every release, and IIRC, it has happened with gaim > before. What part of gaim-2.0.0_beta1.ebuild did you miss? And gaim is a package with a very long history of problems that the upstream developers tend to ignore. So please dont add this to portage or if done please get and net-im-gaim@g.o alias so i can filter gaim stuff.
Well, to start with, I'm getting the same crash in this beta as I'm getting in 1.5.
Uhoh -- gaim-2.0.0_beta1 won't backtrace when started with gdb and built with debug USE flag.
(In reply to comment #2) > Initial ebuild > * Addedd mono, dbus and vv EUSE > I do not believe that it is worth adding in the vv EUSE yet as the vv support is not actually in Gaim yet (visit their IRC channel to confirm this). There is another ebuild on the forums (see http://forums.gentoo.org/viewtopic-p-2963758.html#2963758) that has a few extra EUSEs (ao, audiofile, dbus, startup-notification, xscreensaver, truespeech and mono) though I've removed vv from that version. Should I bug-report the other ebuilds that we have created in there for some of the plugins? (guifications, gaim-xmms-remote, slashexec) gaim-otr do not seem to have updated yet. (In reply to comment #4) > I'm pretty sure that at least for dbus, it depends on a specific version since > the API has changed. I will try to ask a dev about the exact requirements later if it would help?
The ebuild needs to inherit the mono eclass, or else you'll run into a sandbox violation (with USE=mono of course). Apart from that, I tried the ebuild from the forum and it runs fine here on ~amd64 (and there are quite a few new nifty features!)
(In reply to comment #15) > The ebuild needs to inherit the mono eclass, or else you'll run into a sandbox > violation (with USE=mono of course). > Cheers, I've added that to my forum version. (In reply to comment #4) > (In reply to comment #2) > > Initial ebuild > > * Addedd mono, dbus and vv EUSE > > I'm pretty sure that at least for dbus, it depends on a specific version since > the API has changed. > I've added the dependancy for dbus in now, it also uses python during installation (for dbus only) so I've added that too.
added :)
~amd64 keyword please, compiles and works fine here: Portage 2.1_pre1 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.6-r1, 2.6.14-gentoo-r5-david x86_64) ================================================================= System uname: 2.6.14-gentoo-r5-david x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.0_pre11 dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -fomit-frame-pointer -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon64 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks fixpackages sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.linux.cz/pub/linux/gentoo http://mirror.gentoo.sk/pub http://distfiles.gentoo.org/" LANG="cs_CZ.UTF-8" LC_ALL="cs_CZ.UTF-8" LINGUAS="cs" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://mirror.gentoo.sk/gentoo-portage" USE="amd64 X aalib acpi adns alsa apache2 apm audiofile avi bash-completion berkdb bitmap-fonts bzip2 caps cdparanoia cdr cups curl curlwrappers dbus dga dio directfb divx4linux dts dvd dvdr dvdread emboss emul-linux-86 encode exif fbcon ffmpeg flac flash foomaticdb fortran ftp gd gdbm gif gpm gstreamer gtk gtk2 hal icq id3 id3v2 imagemagick imlib innodb ipv6 jabber javascript jpeg kde kdeenablefinal lame lcms libcaca libwww lm_sensors lzw lzw-tiff mad matroska mbox mikmod mime ming mng mp3 mpeg mplayer mysql mysqli ncurses nls nowebdav nptl nptlonly nvidia ogg oggvorbis openal opengl osc oscar pcntl pcre pdflib perl php pic png posix ppds python qt quicktime readline real recode sdl session skey slang slp sockets sox speex sqlite ssl svg symlink tcpd theora threads tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales utf8 vcd vorbis wmf xine xml xml2 xpm xv xvid zlib elibc_glibc kernel_linux linguas_cs userland_GNU" Unset: ASFLAGS, CTARGET, LDFLAGS
gothgirl: PLEASE put gaim-2.0 in package.mask and if you intent on maintaining gaim .. you should add yourself to the net-im herd, there are quite a few related packages.
Also, as noted before, please inherit the mono eclass in the ebuild. Otherwise it dies with access violations.
Fixed to inherit mono eclass and added to package mask
I've the same error in bug #116124 What is gaim-0.76-xinput.patch? PS: I'm trying without patch
An old patch for cjk use flag... No wonder the patch fails, this part of the code looks like it has been quite reworked (the key to send messages is now pulled from the gtk theme, not gaim itself). I did not run into this problem since I don't have cjk in my use flags and milkman's ebuild does not contain the corresponding line ;)
Can the EUSE vv please be removed from the ebuild in portage. Gaim does not support vv at the moment and is not likely to for a while. All it does at the moment is require the user to have a couple more packages installed (which the ebuild does not depend upon correctly). (In reply to comment #23) > I did not run into this problem since I don't have cjk in my use flags and > milkman's ebuild does not contain the corresponding line ;) > I've spoken to Kathryn Kulick (maintainer) and hopefully some of my ebuild will make it into portage.
Created attachment 75202 [details] gaim-2.0.0_beta1-r1.ebuild Updated EUSE dependancies Removed cjk patch EUSE added: ao, audiofile, dbus, startup-notification, truespeech, xscreensaver EUSE Removed: vv
vv use flag is gone gothgirl: please test every new use flag you add....
There are too many useless USE flags in the current ebuild. ao and audiofile aren't really needed, as they control the sound notifications for incoming messages. Also, startup-notification shouldn't be optional as it's an extremely small library that both major DEs use. Since all those aren't turned on by default the basic functionality that a simple "emerge gaim" would produce is crippled. So, please remove these (as was done with the 1.5.0 ebuild :-).
Also, xscreensaver shouldn't be a USE flag. See Bug 86346.
Firstly, sorry if these are silly/nieve questions. I'm new to ebuilding as everyone once was. (In reply to comment #27) > There are too many useless USE flags in the current ebuild. ao and audiofile > aren't really needed, as they control the sound notifications for incoming > messages. I'm not quite sure how to respond.. They control the sound notifications.. yes.. and I understand that they will be chosen for you automatically if either ao/audiofile are present. But how do people know that either can be used if we do not tell them? > Also, startup-notification shouldn't be optional as it's an extremely > small library that both major DEs use. What's a DE? Should size really matter? I thought that use flags represented the packages and features that a package uses? > Since all those aren't turned on by default the basic functionality that a > simple "emerge gaim" would produce is crippled. If an EUSE is not turned on then you've either not installed the package that it matches or you've not set it to come on. If you've not installed the package then it won't get picked up by configure. So what's the difference in functionality? > So, please remove these (as was done with the 1.5.0 ebuild :-). I'll go with whatever the clever people say. If the right people want it to happen then it'll happen anyway. I thought that gentoo was a distro for developers (in some ways also a step down (or forward) from slackware). Surely it is ebuild maintainer's jobs to make sure that the developers have all the options available to them that they would if they compiled the package by hand. Portage should not dumb down the process or remove options, but instead facilitate and help it! Well that's my 2-pence anyway. Answers on a post card please :-)
The first one is really just a misunderstanding -- both ao and audiofile are needed in order to support sound in Gaim. Audiofile is used to access the sound files, and ao is used to output them to the sound device. You can't use only one of them. About startup-notification: my point was that there is no reason anyone would want that turned off. It's grown to become a standard feature, like cut-and-paste. I don't know why the Gaim developers keep it optional, but I don't think I've ever seen that as an option in an ebuild. [By the way, DE stands for Desktop Environment.] The main issue here is that Gentoo isn't about making *EVERY* byte optional, it's about giving control to the user/admin. USE flags that aren't useful to anyone simply don't make sense, that's all. Anyway, good luck -- we're all beginners one time or another... :-)
(In reply to comment #30) > The first one is really just a misunderstanding -- both ao and audiofile are > needed in order to support sound in Gaim. Audiofile is used to access the sound > files, and ao is used to output them to the sound device. You can't use only > one of them. Fair enough. That would be my bad :-( > About startup-notification: my point was that there is no reason anyone would > want that turned off. It's grown to become a standard feature, like > cut-and-paste. I don't know why the Gaim developers keep it optional, but I > don't think I've ever seen that as an option in an ebuild. [By the way, DE > stands for Desktop Environment.] Not everyone uses the main two DE's. In fact there are a lot of people in the gentoo community who use DE's other than the main two (and a lot that don't). I personally use KDE and Openbox (depending on my mood/need). Openbox has the startup-notification use flag. Could the same be said about openbox, should that have the startup-notification flag removed? Anyway, arguing for the sake of arguing now *sigh* > The main issue here is that Gentoo isn't about making *EVERY* byte optional, > it's about giving control to the user/admin. USE flags that aren't useful to > anyone simply don't make sense, that's all. > > Anyway, good luck -- we're all beginners one time or another... :-) > Cheers :-)
This bug was resolved and fixed. But are the ao, audiofile, and startup-notification use flags going to be removed?
It has been done in -r2 :) Sorry for delays, but with holidays and sickness I'm a lil slow...
