Separate in universal and distro-specific parts. Release to CPAN as universally consumable (maybe including e.g. an init-script only in an "examples/" dir), and create Debian-specific setup (which includes init script and logrotate hints) in a Debian package built from the CPAN release.
Seems to me that Daemon::Control is specifically for having code integrate with sysV start-stop-daemon system. Leave it open to users of your CPAN project how to start the daemon - some may favor systemd, runit or maybe plain starting from the commandline.
Consider if relevant to also support alternate admin-controlled system-wide use (e.g. static data below /usr/local/share instead of /usr/share and dynamic data below /var/local instead of /var/lib).
If your daemons make use of external data files, consider use File::ShareDir::ProjectDistDir, or for data potentially overridable by the user consider use File::BaseDir instead.
Hope that helps :-)