It is just strange that I was not pinged authomatically as the code owner.

Only Infinisil was detected as code owner by GH.

Turns out there are a few parts not quite working yet - main features such as recording and motion detection are though. I need to fix those up before we merge.

@volth, any nicer way to handle PERL5LIB and the move to -I as done in the installPhase of zoneminder?

I was able to sucessfully run this on a Raspberry Pi 3 on aarch64. However there were some issues I ran into:

1. I had to disable the tests/checks for the perlPackages.SysCPU packages as they seems to fail on aarch64. @volth I think perl packages are not run on hydra for aarch64, do you know why?

2. I had to figure out how to configure MySQL/MariaDB first as the service doesn't automatically configure the database. @peterhoeg This might be a nice enhancement.

Sorry, I don't know why Hydra doesn't build the perl packages for aarch64. Perhaps @grahamc knows?

I had to disable the tests/checks for the perlPackages.SysCPU packages as they seems to fail on aarch64. I think perl packages are not run on hydra for aarch64

Isn't the case that the packages are not built on aarch64 because the tests fail (for whatever reason)?

I had to figure out how to configure MySQL/MariaDB first as the service doesn't automatically configure the database. This might be a nice enhancement.

The DB user used by ZM shouldn't have permissions to create databases and database users. Of course we could use the nixos mechanism to create the db, but that assumes that the database is on the same host. This is the reason I didn't do this as my ZM install is different from the DB. Maybe the nicest option is to update the description for enable to inform the user and add a new option to create the database. Any thoughts?

In any case, I have just pushed the latest iteration. Working here on amd64.

@peterhoeg Just out of curiosity: did you look at all into declarative camera configuration? This is by no means a feature request, just a question.

did you look at all into declarative camera configuration

I thought about it, but didn't look into it. ZM is a bit of a mess where some things are defined at compile time, some things can be overridden using config files and most things are in the database.

The way to do cameras would be to define them in an attrset and generate the required sql (I understand mysql understands some variation of UPSERT).

I thought it was more important to get it out there first. We can always add features!

The patching of the package and the nixos module are both ugly - I'm very open to feedback to make this nicer.

I think getting ZM packaged is important so I am going to go ahead an merge this. Let's get some people using it and then make things nicer.