Hi, please include this ebuild into the main portage tree, under media-sound/walkzor. Walkzor is an audio file converter, currently supporting mp3 and ogg. One can convert a directory recursively from one format to another, or even from one format to the same (resampling etc). ID3/meta tag support, config file, commandline switches, nice portage-like colored output. Supports gettext and already has a czech i18n (default is en). Written in Python. Thanks, Trancelis
Created attachment 66803 [details] walkzor-2.1.1.ebuild
Please fix the following and reopen: * HOMEPAGE needs to be set * SRC_URI is invalid. * KEYWORDS are incorrect. * IUSE needs to be set. * The msgfmt stuff needs to be in src_compile, have error checking and probably adds a gettext dep. * Header is invalid.
Comment on attachment 66803 [details] walkzor-2.1.1.ebuild # Copyright 1999-2005 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/media-sound/walkzor/walkzor-2.1.1.ebuild,v 1.2 2005/08/24 23:30:54 trancelis; Exp $ inherit eutils DESCRIPTION="Audio file conversion tool supporting media tags" HOMEPAGE="http://walkzor.wz.cz/" SRC_URI="http://walkzor.wz.cz/releases/${P}.tar.bz2" RESTRICT="nomirror" LICENSE="GPL-2" SLOT="0" KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc x86" IUSE="" DEPEND="media-sound/lame media-sound/vorbis-tools dev-python/pyvorbis dev-python/pyid3lib sys-devel/gettext" src_install() { dobin walkzor for file in *.po do msgfmt -o walkzor.mo "$file" insinto /usr/share/locale/${file%%.po}/LC_MESSAGES doins walkzor.mo rm -f walkzor.mo done }
Created attachment 66808 [details] walkzor-2.1.1.ebuild partially fixed I don't quite understand that src_compile part ... could you explain please ?
and sorry for that ebuild posted to the comments... I don't bugzilla so much
please help
Okay, never mind, with this response speed it's not worth it. Before you even try to add my ebuild to the tree I'd be releasing 5th another. Bye
Patience... There're something like 600 ebuilds in the list, and much as I'd like to be able to work on them all at once, I can't.
(In reply to comment #7) > Okay, never mind, with this response speed it's not worth it. Before you even > try to add my ebuild to the tree I'd be releasing 5th another. Bye Please understand, that fixing your broken ebuild is not developers' duty, it's purely voluntary help. Instead of complaining here you could meanwhile read some docs on writing ebuilds [1], have a look at current ebuilds in the portage tree and try to fix the remaining problems. [1] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 http://dev.gentoo.org/~plasmaroo/devmanual/ http://dev.gentoo.org/~liquidx/ebuildmistakes/