| Summary: | libbtctl and gnome-bluetooth ebuilds | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | John Mylchreest (RETIRED) <johnm> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | nuno.araujo, paradoxx |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
ebuilds
gnome-bluetooth-0.4.1.ebuild libbtctl-0.3.ebuild |
||
|
Description
John Mylchreest (RETIRED)
2003-07-11 12:42:36 UTC
Created attachment 14388 [details]
ebuilds
please attach the ebuild plaintext Created attachment 14441 [details]
gnome-bluetooth-0.4.1.ebuild
Created attachment 14442 [details]
libbtctl-0.3.ebuild
okay, check your redundant deps (libgnomeui brings in the bonobo bits). no need to define RDEPEND="". are there any docs provided? if so specify them with DOCS="" and the gnome2 class will take care of them. if you clear up just these small things it makes it easier for us to consider them for portage purely on the app/stability and whether it fits in. thanks. With all due respect, i feel that the dependancies listed should be left in, with them being direct dependancies of the build. I would hate to see libgnomeui get changed or what have you, for whatever reason, and for it to not pull in other requirements (whether by name or version) RDEPEND was just there as originally i put in RDEPENDS :) Im not aware of any docs being available as of last posting. *** Bug 27146 has been marked as a duplicate of this bug. *** john, our problem here is that we dont have any bluetooth devices to test with, which makes maintenance harder for us (checking new versions etc). would a possible solution be for you to maintain it, but put it under the gnome herd, or something along those lines ? if your happy enough for this to happen. sure, not a problem. Im unable to handle anything today. my schedule is chocka. Ill get all this sorted :) the docs we speak of (#5) are things like README, NEWS, etc. Those docs should be provided and they are there. That should be fixed. Dependencies : >=<pack>* is redundant, >=<pack> is enough . * Should only be used with = really . After a quick check, the gnome-bluetooth deps seem to be lacking. I miss libglade, gnome-vfs, librsvg and some non gnome related (not looked into that, so don't pin me on those) deps. buildtime deps are at least intltool-0.18 and pkgconfig , which are missing. Is there a good reason to leave the MAKEOPTS in ? Since this ebuild is copied from libgtkhtml3, make sure its really needed and not cruft. These flaws were found after a quick examination of the gnome-bluetooth package only. This need to be properly fixed first before we discuss how and where this goes into the tree and who is going to take care of them. is this bug in the libbtctl-0.3.ebuild? root@golab golab # emerge -p libbtctl-0.3.ebuild These are the packages that I would merge, in order: Calculating dependencies \!!! aux_get(): ebuild for 'home/libbtctl-0.3' does not exist at: !!! /usr/portage/home/libbtctl/libbtctl-0.3.ebuild emerge: create(): aux_get() error on home/libbtctl-0.3; aborting... and i get emerge gnome-bluetooth-0.4.1.ebuild Calculating dependencies \!!! aux_get(): ebuild for 'home/gnome-bluetooth-0.4.1' does not exist at: !!! /usr/portage/home/gnome-bluetooth/gnome-bluetooth-0.4.1.ebuild emerge: create(): aux_get() error on home/gnome-bluetooth-0.4.1; aborting... no this is not a bug in the ebuild. /usr/portage/home/libbtctl/libbtctl-0.3.ebuild isnt a valid path to the ebuild, as home isnt a valid category. the best solution is to define a PORTAGE_OVERLAY directory in your /etc/make.conf and then within that create the category/application directories within which you place the actual ebuilds. just to chime in, i recently got a bluetooth dongle and a bluetooth enabled phone, so i could probably do some testing on this .. but to be honest, it wouldn't be high on my list of priorities. i've added libbtctl and gnome-bluetooth to net-wireless now. and they seem to work pretty well with my bluetooth phone. fixed the issues with the ebuilds regarding the over specified dependencies (eg. libbtctl only needs glib and not bonobo, etc) and the DOCS issue. the MAKEOPTS need to stay because they fail to compile using anything about -j2. ehm, you still lack half the deps afaics and DOCS as well. (gnome-bluetooth check) and i like to see the herds discussed, cause i don't think this should be primarily gnome's responsibility. Have the other herds been informed about you adding them ? i'm in all three of the herds .. i'm taking care of bluetooth stuff from wireless and i consider phones as a part of pda. (seemingly there isn't a better herd right now for phone related ebuilds) so what would you like to discuss? yeah, you were right about the docs, i missed out the NEWS and the AUTHORS stuff. fixed in libbtctl and gnome-bluetooth ok .. deps and stuff taken care of now .. closing haw sombodey added it to emerge sync server yet?.. i tinc the haw bin som updatest to the prog the last days go to the home page to luc.. u can u alwasy join the e-mail list to the prog.. old e-mail to the email list http://lists.usefulinc.com/pipermail/gnome-bluetooth/ Has anyone ebuilds for libbtctl 0.4 and gnome-bluetooth 0.5. These seem to use the new 2.7 Bluez-Utils, as Bluez-sdp is deprecated. |