AnsweredAssumed Answered

Dealing with Mac files when creating module loadable packages

Question asked by Tom Noel on Feb 17, 2017
Latest reply on Feb 17, 2017 by Christos Pagonidis

Often when trying to create a module loadable package I will end up with the Mac generated files such as .DS_STORE among many others.  This is not an issue if I'm loading in a local environment since I can turn off the package scanner, but the package will fail in an on demand instance.  How do you other Mac developers deal with this when creating module loader packages?

 

Currently my annoying but functional solution since I store all my change on github is I just hop over to my windows virtual machine, download the latest commit, & create/upload my package from there.

 

I'd prefer to be able to do all this from the Mac interface.

 

Thanks,

Tom Noel

Outcomes