Combined with what I had already seen, we need to move the cinnamon gir to a private path, then once done I can move it to cinnamon-common to align with the upstream.
Cinnamon girs are not used by other packages or non-packaged software but only recently added upon request and therefore used only in rare cases by developers (based on what I found). So I don't think it's a problem for them to do additional manual operations such as installing the necessary -dev packages. If it were up to me it wouldn't be a problem to add the cinnamon-dev package in which to move the girs and have all the necessary dependencies but I fear that the upstream wouldn't want it and I want to avoid confict with upstream is possible. However there doesn't seem to be a need for this package if I'm not mistaken.
About dh_girepository so is not needed use it with private gir, so I could remove it and it will only be necessary to manage it if any future changes are made that will automatically scan for any gir (even private ones), right? If future changes will scan for private gir add of "--no-dev-dependencies" can be useful but given the rare case it doesn't seem very important to me and we could manage with the override. Or you are sure to do this changes so I keep override to avoid another future fail to build?
About muffin gir private (as actually) is needed for fork of integrated things, muffin packages on debian seems ok now, or I'm wrong? upstream also had improved packaging when a rebase was done, only one thing seems missed, the move of /usr/libexec/muffin-restart-helper out of libmuffin0 package (upstream moved from muffin package to libmuffin0 in 4.0 and keeped it). On debian packages we don't moved same of upstream or it would go against shared library package policies. or am I wrong?
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature