Created attachment 477982 [details] bluez-tools-0.2.0 ebuild New package request for bluez-tools that is needed by latest net-wireless/blueberry version. I am OK to proxy maintain it like I do for net-wireless/blueberry. I attach an ebuild proposal.
Created attachment 477984 [details] metadata.xml Metadata file for bluez-tools package
(In reply to charlot from comment #0) > Created attachment 477982 [details] > bluez-tools-0.2.0 ebuild > > New package request for bluez-tools that is needed by latest > net-wireless/blueberry version. > > I am OK to proxy maintain it like I do for net-wireless/blueberry. > > I attach an ebuild proposal. Thank you for the ebuild, some (minor) comments SRC_URI="https://github.com/khvzak/${PN}/archive/${COMMIT}.tar.gz -> ${PN}-${PV}.tar.gz" ^ any reason not to use ${P} above instead of ${PN}-${PV} ? LICENSE="GPL-2" ^ seems this should actually be GPL-2+ based on the headers in the .c files I looked at?
(In reply to Kristian Fiskerstrand from comment #2) > SRC_URI="https://github.com/khvzak/${PN}/archive/${COMMIT}.tar.gz -> > ${PN}-${PV}.tar.gz" > ^ any reason not to use ${P} above instead of ${PN}-${PV} ? No you are right, we should use ${P}. Besides, the versioning scheme I used is not the best since it seems the 0.2.0 version has never been officially released. The best is to prefix the name of the ebuild with _pre20161212 according to the date of the commit. > LICENSE="GPL-2" > ^ seems this should actually be GPL-2+ based on the headers in the .c files > I looked at? OK I will attach a new version of the ebuild regarding your two comments.
Created attachment 477994 [details] bluez-tools_pre20161212.ebuild Updated version of the ebuild
(In reply to charlot from comment #3) > (In reply to Kristian Fiskerstrand from comment #2) > > > SRC_URI="https://github.com/khvzak/${PN}/archive/${COMMIT}.tar.gz -> > > ${PN}-${PV}.tar.gz" > > ^ any reason not to use ${P} above instead of ${PN}-${PV} ? > > No you are right, we should use ${P}. Besides, the versioning scheme I used > is not the best since it seems the 0.2.0 version has never been officially > released. The best is to prefix the name of the ebuild with _pre20161212 you'd use _pre if you're getting closer to a released version (e.g knowing it is an rc variant), what you likely want to look into is 0_pYYYYMMDD (note that your current name is invalid as it has no version)
Added, for updates, please provide a git format-patch against the gentoo git repository including commit message describing the change. commit 101965a9308cb82d3fa1234177905a80000b0fc5 (HEAD -> master) Author: Kristian Fiskerstrand <k_f@gentoo.org> Date: Sun Jun 25 21:45:43 2017 +0200 net-wireless/bluez-tools: New package Needed by net-wireless/blueberry Gentoo-Proxied-Maintainer: Olivier Laurantin Gentoo-Bug: 622698 Package-Manager: Portage-2.3.6, Repoman-2.3.1