Created attachment 382322 [details] libomron-0.9.0.ebuild This is an extremely simple but working ebuild for extracting data from medical devices such as blood pressure measurement kit by the Japanese company Omron. The original software has been written by qDot, I have only prepared this ebuild. I am not sure about the app-misc placement, but it doesn't seem there is a more appropriate category right now. Perhaps worth creating something for *medical* software?
Comment on attachment 382322 [details] libomron-0.9.0.ebuild >EAPI=4 Why not jump straight to the latest, EAPI=5? >DESCRIPTION="Library and tool set for extracting data from Omron medical devices via USB." Shouldn't end in a dot. >HOMEPAGE="http://sourceforge.net/projects/nplabs/files/libomron/0.9.0/" This should probably reflect that development has moved to github. Although over there it says it forked from https://github.com/openyou/libomron >SRC_URI="mirror://sourceforge/nplabs/libomron/${P}.tar.gz" Same. >LICENSE="GPL-2" >SLOT="0" >KEYWORDS="~amd64" >IUSE="swig" > >RDEPEND=" > dev-util/cmake > dev-lang/python > dev-libs/libusb > swig? ( dev-lang/swig )" That looks fishy. What happens differently when dev-lang/swig isn't around? Why is the RDEPEND on swig needed? I guess the metadata.xml entry would explain?
Thanks for the prompt response. Nothing wrong with EAPI=5, I can change that, I was following the dev guide as it's been a while since the last time I did an ebuild. Minor fixes - ok. As for swig - I've no idea. The README says it is optional, cmake makes a check for it but it works for me without it in the same way. If you want I can remove this IUSE...
Created attachment 382326 [details, diff] patch addressing the suggestions
Created attachment 382330 [details] improved ebuild
Created attachment 382332 [details, diff] improved patch
Created attachment 382334 [details, diff] improved patch
