There is a newer version of Gnomad out. Version 2.8.3 to be exact. This version includes preliminary support MTP devices such as the Creative Zen Sleek Photo. Would be nice if we could have a updated ebuild.
(In reply to comment #0) > There is a newer version of Gnomad out. Version 2.8.3 to be exact. > > This version includes preliminary support MTP devices such as the Creative Zen > Sleek Photo. > > Would be nice if we could have a updated ebuild. > I second this request; however, MTP support is based on libmtp (http://libmtp.sourceforge.net/), which does not currently exist in portage. A new libmtp ebuild would therefore be required, and ideally, mtp/njb useflags would be added to choose the prefferred libraries to build against.
Please note that the linked bug (URL field) blocks adding the libmtp ebuild, at least for me. As my test device (Zen Vision 30GB Black) is MTP-only, the library will need to be able to communicate with it before the ebuild can be committed.
Created attachment 86772 [details] libmtp-0.0.5.ebuild Preliminary libmtp ebuild; media-libs/libmtp
I've noticed that your libmtp ebuild is masked with "~ppc" keyword. I had to manually edit the ebuild file and add "~x86" so that portage would allow me to unmask and compile it.
*** Bug 135583 has been marked as a duplicate of this bug. ***
Created attachment 88614 [details] gnomad-2.8.5.ebuild ebuild for gnomad-2.8.5
Created attachment 89710 [details] libmtp-0.0.8.ebuild
Created attachment 89711 [details] gnomad-2.8.5.ebuild Please note that this ebuild is not ready for merging. The application needs to be run as root for MTP functionality to work at all. This is not acceptable from a security point of view.
I'd like to add that there is Gnomad 2.8.6 out already, which fixes new bugs and incorporates the newest libmtp. It would be nice to make it available via ~x86 at least. Regards, airflow
Created attachment 91123 [details] libmtp-0.0.9.ebuild This updated ebuild enables/installs udev support. It's molded very close to the libnjb ebuild being that both libmtp and libnjb have a common developer upstream.
Created attachment 91124 [details, diff] udev-permissions.patch This patch modifies the generated udev rules to match the standard gentoo pluggable device permissions (group=plugdev, permission 660).
Also, just an FYI, changing the name of the gnomad 2.8.5 ebuild posted here to 2.8.6 allows for a successful install. gnomad works for my Zen Vision:M as a non-root user belonging to the plugdev group using the aforementioned libmtp ebuild and udev patch.
I no longer have any NJB/MTP hardware, so I am releasing maintainership of this package.
The libmtp ebuild lacks the ~amd64 keyword, but both ebuilds (libmtp-0.0.9 and gnomad-2.8.6) work for me (amd64 system, gcc 4.1.1).
Created attachment 94323 [details] libmtp-0.0.11.ebuild
Comment on attachment 94323 [details] libmtp-0.0.11.ebuild Bumped the version on libmtp and added ~amd64
Created attachment 94325 [details] gnomad-2.8.6.ebuild Bumped version of gnomad
Can this ebuild be assigned to maintainer-{wanted|needed} for submittal to the gentoo-sunrise project?
(In reply to comment #19) > Can this ebuild be assigned to maintainer-{wanted|needed} for submittal to the > gentoo-sunrise project? Nope, Sunrise is not for stuff that's in portage.
from the sunrise webpage (http://www.gentoo-sunrise.org/sunrise/wiki/HowToCommit) and i quote: "How To Commit What needs to be done beforehand: * You need a bug for every ebuild. If there is no bug, file one. * Make sure the ebuild is not already in portage, OR updates an existing package that NEEDS a new maintainer ..." and from comment #14, Tony released maintainership of this package.
I frankly dont really mind if it's in sunrise or not, I'm just trying to get more visibility of this new ebuild along with the libmtp library to hopefully get it into the main portage tree. just trying to help.
Comment on attachment 94323 [details] libmtp-0.0.11.ebuild 0.0.16 is in the official portage tree. I didn't know about this bug when I added the ebuild, so I didn't catch the udev permissions thing. I'll add the udev permissions patch to the official ebuild later tonight.
Created attachment 96904 [details] gnomad-2.8.8.ebuild I re-worked the dependencies for this new version according to http://gnomad2.cvs.sourceforge.net/*checkout*/gnomad2/gnomad2/README gconf wasn't needed as a dependency. The "njb" USE flag wasn't used or needed. gnomad depends on libnjb regardless of whether we want to use an NJB device or not. gnomad will build with gtk-2.6 or gnomeui alternatively, which is reflected in the new RDEPEND.
gnomad 2.8.9 is out.
I can confirm that I have used the ebuild, renamed for 2.8.9 version and working with a Creative Vision M. All works fine, a bit slow on transfer but no errors as yet.
I've used that ebuild too (together with libmtp 0.0.20) to get my Creative Zen Microphoto attached. Works fine for me, please include the 2.8.8 ebuild for 2.8.9 in the tree.
I'm working on an ebuild for gnomad 2.8.11, please be patient, the configure script is a challenge in itself. Currently, mtp inclusion is automagic and needs to be both specified with a use flag, and that use flag actually needs to take effect when configure runs. I'm patching the configure script to make it work and hopefully upstream will accept it (regardless it'll be here with the build). gnomad 2.8.11 will require libmtp 0.1.2 or better (0.1.3 is in portage, under package.mask). I will tidy up some bugs with libmtp 0.1.3 soon; metalgod will be my proxy with the libmtp stuff and will work with the sound group on getting this updated gnomad ebuild into the tree.
*gnomad-2.8.9 (24 Oct 2006) 24 Oct 2006; Thomas Matthijs <axxo@gentoo.org> +gnomad-2.8.9.ebuild: version bump
