Adding two (different) copies of same installer pkg and same version

[John Lockwood]

This issue seems somewhat similar to a previous discussion located at -

https://groups.google.com/g/autopkg-discuss/c/MML_Tr_4Y48

However. in my case whilst the two installer packages are the same name and the same version they do have different checksums.

The installer(s) in this case are auto-generated MunkiReport client installers. They are generated from the same MunkiReport server and hence the same version, however I have used different AutoPkg Munki override recipes to in theory configure the building of slightly different installer packages - the significant difference being a difference set of defined modules to use between the client and the MunkiReport server.

By necessity I am having to build two separate MunkiReport servers with one being on a non-Internet connected network. I have already built a similar setup for two separate Munki servers to do difference apps and updates by using two different sets of manifests and periodically replicating the Munki Repo between the two networks and servers via an external drive and this for Munki is working fine. I am now wanting to do a similar exercise for MunkiReport. That is not to replicate the MunkiReport data but to have two MunkiReport client installer packages with each copy set to the appropriate networks manifest.

I have been able to manually add the second pkginfo and pkg and this seems to have worked, I updated the Installer Item Hash in the second pkginfo and I have different names set and different repo folders. This seems to have worked manually the resulting installer pkg via Munki installed fine and has correctly configured the first and so far only test client. 

It would however be 'nicer' if the AutoPkg override recipes allowed adding both without having to do this manual exercise.