gnome-phone-manager (v0.3) is a tool that would be nice to have in portage. I have created an ebuild and a patch for it which I'll attach to this bug report. At the moment I have placed it in net-wireless. Dunno if that is correct though... This ebuild depends on BUG 53549 i.e. the ebuilds for libbtctl-0.4.1 and gnome-bluetooth-0.5.1 should be incorporated into portage at the same time. It's marked ~x86 atm.
Created attachment 33584 [details] gnome-phone-manager-0.3.ebuild
Created attachment 33585 [details, diff] gnome-phone-manager-0.3-gcc3.patch A patch that makes gnome-phone-manager compile against gcc3.
Created attachment 33628 [details] Updated ebuild Seems it doesn't compile with >=libsigc++-2.0, this ebuild forces 1.2.5 and it compiles at least...
Created attachment 33949 [details] gnome-phone-manager-0.4.ebuild * Bumped the version. * Changed so that the patch is applied even though version was bumped.
Ebuild looks good. Would be nice to get this into portage. I made an ebuild myself - virtually identical to attached except without the gcc3 patch. I found it compiles fine unpatched with /gcc version 3.3.3 20040412 (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6/. A problem I did have was that it didn't compile against gsmlib-1.11_pre030826 which is currently marked stable in portage. 1.10 didn't compile either due to a missing #include (perhaps a gcc3 thing?). Please see Bug 54993. Am I wrong? An issue I did have at runtime was that phonemgr couldn't bind to /dev/rfcomm0 because the device didn't exist. a mknod && chown fixed that, but it'll probably vanish after a reboot due to devfs, right? What's a nice elegant way to deal with the absence of this device file?
One more thing: after sending and receiving a few SMS messages via bluetooth, the phone (T610) kind of jammed its bluetooth. Every operation to do with bluetooth (except remove device) was disabled because the phone thought it was busy. Had to turn off/on to reset. Anyone else seeing this behavior? If not, I'll assume its the phone - the firmware has exhibited a few other bugs so this wouldn't surprise me.
1. You need the patch to compile gsmlib yes. 2. I use udev so rfcomm is created automatically for me. 3. Make sure your T610 has the latest firmware (you can update it in most Ericsson service centers). I think it might be a phone problem. I don't have that problem with my T630.
in latest ebuild, "ORBit2-2" should be changed to "orbit-2" as it has been renamed
adds dependency on newest gsmlib snapshot
Yeah, i'm still waiting for this ebuild to be moved into portage. I tested this tool using udev today. You can create a permission for udev in /etc/udev/permissions.d/50-udev.permissions or create your own 51-udev.permissions like rfcomm*:root:bluetooth:0660 Add a group bluetooth and add yourself to it and gnome-phone-manager works for users, which are in group bluetooth, too. Yea, this is NO bug-report but rather an wish to get this thingy into portage. It works awesome. With devfs, I didn't really try it, as it, even as root, didn't work for me.
Created attachment 53942 [details] gnome-phone-manager-0.4.ebuild Obsoletes attachment #33949 [details]. * Updated copyright line * Removed gnome-bluetooth $ Header: $ junk * Fixed orbit dependency * Bumped gsmlib dependency to gsmlib-1.11_pre041028
Any news on this?
Not GNOME, reassigning
commited as net-dialup/gnome-phone-manager
Thanks a lot Alin, I was wondering if this should be net-wireless though. Just curious.
you're right. I've moved it to net-wireless/gnome-phone-manager, under mobile and gnome herd control. if you already installed it, run emerge -C gnome-phone-manager emerge sync emerge net-wireless/gnome-phone-manager The net-dialup package had a too short life to worth a proper move. mobile guys, hope I didn't pissed you off ;)
Please do not assign ownership of packages to the mobile herd without consulting us first when you're not in the herd - we have enough packages to maintain as it is (and this packages is way beyond our field, which is mobile computing, not cell phones). Why was this package moved to net-wireless? The original net-dialup category seems far better to me - or perhaps app-pda? Please remove the mobile herd as maintainer.
I suggested net-wireless as it basically works with gnome-bluetooth etc. It also allows syncs over Serial ports, so I'm lost. Almost all Bluetooth stuff is on net-wireless btw.
OK, changed herd back to net-dialup. I was going to become member in mobile for helping you with your 80+ bugs, you know. since this package is about controlling a cell phone over bluetooth, I guess it has nothing to do with net-dialup (which is about serial lines, modems, DSL, ISDN).
The mobile herd is for mobile computing, not mobile phones. If every application, that somehow works with either 802.11, bluetooth or IrDA should be in net-wireless/ ... that would be like putting everything, that have been internationalized into app-i18n/. Take app-pda/* for example - many of the applications in there works with bluetooth, yet they have nothing to do with the low-level bluetooth stack. Same goes for gnome-phone-manager.
i think this is more relevant in app-pda more than net-wireless. since you're talking about a phone book management software.
