It seems, that zc030x webcams are currently not supported by Gentoo. Reproducible: Always Steps to Reproduce: Plug cam in. Nothing happens. Actual Results: Nothing. Expected Results: Load a driver for the USB device.
Created attachment 64386 [details, diff] I used the CVS from 26 Jul 05 of http://zc0302.sourceforge.net/zc0302.php?page=download to create a dummy 0.1 version. I'd like to create something like a zc030x-26072005 version, but ebuild won't unpack this here due to naming errors. I'm a newbie to ebuild writing, so I don't have much clue how to fix this at the moment. Since I consider this a hack, I don't want to add this to portage, before any experienced Gentoo developer has reviewed it. TIA
The ebuild is totally unreadable, please attach something useful and reopen then.
(In reply to comment #2) > The ebuild is totally unreadable, please attach something useful and reopen then. I just looked over the ebuild and I'm not sure what your problem is? =============================================== # Copyright 1999-2004 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: $ inherit linux-mod DESCRIPTION="driver for webcams with zc030x chip" HOMEPAGE="http://zc0302.sourceforge.net" SRC_URI="http://zc0302.sourceforge.net/release/zc030x-driver-0.1.tar.bz2" S="${WORKDIR}/zc030x" LICENSE="GPL" SLOT="0" KEYWORDS="x86" IUSE="" DEPEND="" MODULE_NAMES="zc030x(kernel/drivers/usb/media/:)" pkg_setup() { linux-mod_pkg_setup BUILD_PARAMS="KSRC=${KV_DIR} KDIR=${KV_DIR}" } src_compile() { linux-mod_src_compile } src_install() { linux-mod_src_install dodoc CHANGELOG } =============================================== What part of the ebuild caused you problems? The faked source URI?
(In reply to comment #3) > I just looked over the ebuild and I'm not sure what your problem is? > What part of the ebuild caused you problems? > The faked source URI? My problem is that I see just some unreadable binary mess. If that is a tarball, then you have set incorrect mime type for the attachment, and also we don't want any tarballs, just plaintext ebuilds. Re-attach a *plaintext* ebuild; if there is no homepage, attach the driver tarball as a separate attachment and be sure to set correct mime types for both.
> My problem is that I see just some unreadable binary mess. If that is a tarball, > then you have set incorrect mime type for the attachment, and also we don't want > any tarballs, just plaintext ebuilds. Uh...ok. The original attachment was a zipfile containing the ebuild, the tar.bz2 of the driver, the metadata, digest etc. > Re-attach a *plaintext* ebuild; if there is no homepage, attach the driver > tarball as a separate attachment and be sure to set correct mime types for both. Sorry, I thought I had set the correct mimetype, so I was somewhat irritated about your comment. Should I attach all the files separately? Wouldn't it be easier to mail you the zipfile? The problem is, that there's no release of the driver at the homepage, so I had to make my own release. The ebuild won't help you that much, because of the faked SRC_URI. You'll download a release., but not the current version, that was in my attachment.
No, we don't want zipfiles nor tarballs, we want a plaintext ebuild. We don't need digest and metadata. And I definitely don't want anything mailed to me. http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=3#doc_chap2
