0

My friends are losing points in their computer science classes because their submission graders decompress and read zip files, which are obfuscated by a bunch of Apple metadata crap generated from zipping a file through the right-click contextual menu in Finder.

I've written a bash script to zip only unhidden files from a specific directory, and I've added a contextual menu service through Automator so this script can be run from right clicking a file.

The problem is I don't want to manually copy over all this stuff and make Automations on each computer my friends use. I'd like to leverage make or some similar utility to make an executable that will add the bash file and automator menu service to any computer the executable is opened from.

I'm lightly familiar with make (more familiar with rake), but I can't find out how to package the automator service and install it on their machine through an executable.

user
  • 3,388
  • 7
  • 33
  • 67
  • 1
    `Make` is used when you have source code that needs to be recompiled. You're not doing anything like that - what you want is to create an installer that puts everything into a package and can be deployed easily. – l'L'l Jan 16 '14 at 17:49
  • Thanks for the heads up, I thought make was a packaging utility also. I'm obviously off course, so point me in the right direction if you're familiar with OSX. – user Jan 16 '14 at 19:27
  • Why not just distribute the bash script? If they're computer science students they should get used to using the commandline. – nvioli Jan 16 '14 at 21:03
  • @nvioli, computer science students like to point and click nowadays. :D – l'L'l Jan 16 '14 at 21:08
  • @nvioli - Well, they're computer science students *this* semester – user Jan 17 '14 at 15:20

1 Answers1

2

You'll want to package your automator application and script(s) into an Installer Package (.pkg). The best way to achieve this is to understand some general concepts, the commands to build one, and by checking out some tutorials or other relevant information.

I recommend for creating your first Installer Package using a utility such as Packages (open-source and free), which has excellent documentation, and is less complicated than using the command line tools. Basically it puts a nice gui around the Apple tools which are somewhat nonintutive by themselves.

Building Installer Packages is not the easiest thing to do your first time, and it might take a bit of patience to finally get it right. Once you've successfully created one you should have a good grasp on what is involved in putting them together along with the concept behind it all. At the very least, this information hopefully points you in the right direction regarding your question, and/or gives you a better idea of how to accomplish what you want to do.

Community
  • 1
  • 1
l'L'l
  • 44,951
  • 10
  • 95
  • 146