@scriptingosx commented on GitHub:
DEBUG : zoom : DEBUG mode 1, not checking for blocking processes
@acodega commented on GitHub:
Please post a policy result from Jamf or an Installomator log when you can.
@scriptingosx commented on GitHub:
when you install a pkg, it is registered in the system. You can see which pkgs are registered on the system by running pkgutil --pkgs in the Terminal. When…
@Theile commented on GitHub:
And using INSTALL=force will install it no matter if it exists already or not.
@asri-tm commented on GitHub:
Yep confirmed insomnia installs fine for me too on 10.4beta.
2023-05-30 15:41:45 : REQ : insomnia : ################## Start Installomator v. 10.4beta,…
@Theile commented on GitHub:
This script does not notify about anything. Only Installomator is doing that, and it should be told to NOTIFY=all so quite some messages for each software should…
@acodega commented on GitHub:
Ah yes that's correct, it's only designed for one label. The Installomator 1st.. [script in auto-install and SS versions](https://github.com/Installomator/Installom…
@wakco commented on GitHub:
I was hoping to avoid maintaining my own Labels, which oddly enough is part of the point to Installomator in the first place.
I guess I'll just maintain some of my…
@wakco commented on GitHub:
As far as the online infrastructure, that is understandable, as for trust, that already exists as it is.
Another thought might be to seperate the labels into a…
@acodega commented on GitHub:
Trust only exists in that an administrator is manually downloading Installomator.sh and presumably checked the latest commits, or the administrator is installing the…
@macmangr commented on GitHub:
Hi Theile,
using the following options in the script, i thought there should be one notification per label as usual, but only one notification is shown "No…
@scriptingosx commented on GitHub:
This is a good question. Let me explain the motivations here:
This is intentional. The script does what it does as root so we have to take care to know…
@scriptingosx commented on GitHub:
Also, we have already split the labels from the functional code in the main repo, which makes it easier to maintain and merge. the [assemble.sh script](https:/…
@scriptingosx commented on GitHub:
Just to clarify: in my opinion, the option (and actually requirement) to maintain your own labels, was intended from the very beginning.
I would recommend…