Attached is xbindkeys-1.5.5.ebuild (new package). xbindkeys is a program that allows you to launch shell commands with your keyboard or your mouse under X Window. It links commands to keys or mouse buttons, using a configuration file. It's independant of the window manager and can capture all keyboard keys (ex: Power, Wake...). This is my first submitted ebuild, so you may want to check it for correctness.
Created attachment 1634 [details] The ebuild file
Sorry for that.
I added this package to the tree as x11-misc/xbindkeys. Thanks for your contribution. Since this is your first package, i'll tell you something about the modifications i made (maybe you are interested, if you arent - stop reading): >> S=${WORKDIR}/xbindkeys-1.5.5 This is obsolete.If you dont set ${S}, portage will unpack to ${WORKDIR}/${P}. (Which is the same as your S) >> SRC_URI="http://hocwp.free.fr/xbindkeys/xbindkeys-1.5.5.tar.gz" Better write SRC_URI="http://hocwp.free.fr/xbindkeys/${P}.tar.gz" - Its easier to maintenance: You only have to copy the ebuild like that "cp xbindkeys-1.5.5.ebuild xbindkeys-1.8.5.ebuild" and it will still work. (Without editing) >> LICENSE="GPL-2" Very good, keep doing that. (I had to add this to the whole net-misc package, gosh that was some nasty work). I also added these two lines: KEYWORDS="x86" SLOT="0" KEYWORDS = sytem architecture. SLOT="0" means that its not allowed to have another version of the package installed. That was in a mail from drobbins: All ebuilds should define a SLOT variable. The SLOT variable is used to tell Portage if it's OK to keep multiple versions of the same package installed at the same time. For example, if we have a libfoo-1.2.2 and libfoo-1.3.2 ebuilds, it would probably be optimal to instruct Portage to not remove libfoo-1.2.2 if we decide to upgrade to libfoo-1.3.2. To do this, we'd specify SLOT="1.2" in libfoo-1.2.2 and SLOT="1.3" in libfoo-1.3.2. Emerge clean understands SLOTs, and will keep the most recent version of each SLOT and remove everything else. So, in the above example, if we merge libfoo-1.3.3 that has SLOT="1.3", emerge autocleaning will remove libfoo-1.3.2 but keep libfoo-1.2.2. Then, if you we libfoo-1.4.0 with SLOT="1.4", both libfoo-1.3.3 and libfoo-1.2.2 will be kept since they have different SLOT variables. >> src_unpack() You dont need to do that, portage will take care of it. You usually implement your own scr_unpack() when you want to patch the files before compiling them. >> ./configure --prefix=/usr --mandir=/usr/share/man || die Better split the ./configure up to multiple lines. And its nifty to know where the merge died, so write: die "./configure failed" or something like that. >> make DESTDIR=${D} || die We use emake for that. Here 'die "emake failed"' would be nice. >> make DESTDIR=${D} BINDIR=/usr/bin install || die The make line can be split to multiple lines. (And the die again, yes) I hope that i was able to help you. Dont take offense from my comments please, i'm only trying to do you a favor. (Heh, you should've seen my first ebuild ;)) If you have further questions, ask here or in #gentoo on irc.openprojects.net -phoen][x-
