[owfs] missing the python module

[Achrn]

Thanks for the explanation.

Building owfs with python doesn't link anything else into the owfs binary, it builds the python language module that is needed to communicate with owfs from python. That is, if you compile it on a machine with python and then install it on a machine without python, you don't get lib errors and so on.

Python is a requisite of the full owfs system, but the author has written the compile process so that it doesn't error if you don't have python, you just get an incomplete build, though most of it remains functional. I am pursuing discussion with the upstream maintainer, but the problem of an incomplete owfs doesn't apply to ArchLinux, because it doesn't precompile owfs from the PKGBUILD. Python is a 'makedepends' not a 'depends'.

Does ALARM have packages that are not in ArchLinux at all? That is, could I submit a a PKGBUILD for 'owfs-python' that is either a fully functional owfs (which is as intended by the original author, since it's documented on the owfs web site), or just the python module of it? Is it better to submit that to AL AUR first and then propose to bring it into ALARM, or can it just be submitted to ALARM?

[moonman]

You can ask him to add it under makedepends instead of depends https://wiki.archlinux.org/index.php/PK ... akedepends