7

I'm one of the developers on the Motion project.

We are trying to merge the popular motion-mmal fork used by a lot of Raspberry Pi users back into the main project's github repository.

To build with MMAL camera support, the libraspberrypi-dev package is required to be present (and I guess to run, the libraspberrypi0 package needs to be a dependency of the built package too) — so that we can build/run with the MMAL camera interface files.

What is the correct way to achieve this? The libraspberrypi packages aren't present in Debian as a I understand it, so I believe the upstream Debian package can't mention those.

Is the only way to have a completely separate package with a different name that is only available in Raspbian — that seems less than optimal as it means anyone that installs motion will get a version that doesn't support the Raspberry Pi camera, even though the Raspberry Pi support is there in the upstream source code.

I've searched but didn't find much on this subject; https://raspberrypi.stackexchange.com/a/37300/10976 is relevant but I think may be more about the case where the upstream source code doesn't have Raspberry Pi support.

Further confusing me is the fact that raspbian is apparently targeting boards other than raspberry pi, so I don't entirely see how to depend on raspberry pi specific libraries even in raspbian.

Community
  • 1
JosephH
  • 173
  • 7

1 Answers1

6

You're correct that you can't add a build-dependency on libraspberrypi-dev to the Debian package, since there is no such package in Debian. You can't even limit the build-dependency to an architecture since both Debian and Raspbian use armhf (albeit with slightly different definitions).

Technically, it should be possible to provide a Raspbian-specific motion package in Raspbian, in the same way that Ubuntu has Ubuntu-specific versions of packages also available in Debian. However, the FAQ states Raspbian attempts to keep the changes minimal so really you should ask Raspbian.

Stephen Kitt
  • 161
  • 1
  • 3