New Macs – Unzip Omnis

Mike Matthews, September 26 2017 22:57:55

New Macs – Unzip Omnis

Ok, so reading back a bit, OSX and Studio what version? I don’t think it matters.

I currently have done this by using the FileOps commands from the running version of Studio. You know where the comps path is using SYS() functions.

I move the current ones into a new folder called comps-disabled.
Then move the new ones into place.
The restart Omnis.

This worked for v4, v5 and v6 so far, OSX and Windows.

The trick is not to replace a current loaded one, but you can move it around while running. So I move it out, put in the new one, and force the user to restart our App.

This works for Externals as well. Did I get the problem right now?

Mike

Mike Matthews, Managing Director, Lineal Software Solutions Ltd

Apple Reseller, Microsoft Partner, SQLWorks Business Partner
phone: 01271 375999 | web: lineal.co.uk <www.lineal.co.uk/> | email: mike.matthews@lineal.co.uk <mailto:mike.matthews@lineal.co.uk>
> On 26 Sep 2017, at 22:51, Michael Mantkowski <michaelj@clientrax.com> wrote:
>
> Mike,
>
> I think there is a misunderstanding. I am trying to update an already existing instillation.
>
> Just trying to get a few new XCOMP file updates into the exiting OmnisRT.
>
> *********************************************************************
> Michael Mantkowski
> ClienTrax Software
> 1-614-875-2245
> *********************************************************************
>
>
> —–Original Message—–
> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On Behalf Of Mike Matthews
> Sent: Tuesday, September 26, 2017 5:46 PM
> To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
> Subject: Re: New Macs – Unzip Omnis
>
> Michael,
>
> You need to look at and understand the FirstRunInstall mechanism. I think thismighthelp you, the penny finally dropped for me the other day, after a good sound ear bashing by Chris at Omnis Support.
>
> Mike
>
>
>
> Mike Matthews, Managing Director, Lineal Software Solutions Ltd
>
> Apple Reseller, Microsoft Partner, SQLWorks Business Partner
> phone: 01271 375999 | web: lineal.co.uk <www.lineal.co.uk/> | email: mike.matthews@lineal.co.uk <mailto:mike.matthews@lineal.co.uk>
>> On 26 Sep 2017, at 22:36, Michael Mantkowski <michaelj@clientrax.com> wrote:
>>
>> Alex,
>>
>> That would not work because the xcomps reside within the OmnisRT.aps file (package). I don’t want to replace the whole OmnisRT, just the three xcomps the are inside it.
>>
>> But maybe if I manually create the folders the represent the path?
>>
>> I will try that.
>>
>> *********************************************************************
>> Michael Mantkowski
>> ClienTrax Software
>> 1-614-875-2245
>> *********************************************************************
>>
>>
>> —–Original Message—–
>> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On
>> Behalf Of Alex Clay
>> Sent: Tuesday, September 26, 2017 5:29 PM
>> To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
>> Subject: Re: New Macs – Unzip Omnis
>>
>> Hi Michael,
>>
>> Instead of adding the xcomps directly to the payload in Packages, just add the ClienTrax parent folder with the xcomps in their correct sub-folder. The installer should then preserve that subfolder path and install the xcomps in the correct location.
>>
>> Alex
>>
>>> On Sep 26, 2017, at 17:25, Michael Mantkowski <michaelj@clientrax.com> wrote:
>>>
>>> Hi Alex,
>>>
>>> Right – That is what I have done as well. Our ClienTrax folder is always in the Applications folder for all our users over the last 20 years.
>>>
>>> I am adding the files to the “Payload” right from where I would want them to be placed on the customers computer.
>>>
>>> I just can’t figure out how to get the destination location of the xcomp files to be different than the library files.
>>>
>>> I am updating three library files into: /Applications/ClienTrax.
>>>
>>> Then I have three XCOMP fiels that I want to go to:
>>> /Applications/ClienTrax/OmnisRT.aps/Comntents/MacOS/xcomp
>>>
>>> I can’t figure out how to change the “destination” of those three files.
>>>
>>> *********************************************************************
>>> Michael Mantkowski
>>> ClienTrax Software
>>> 1-614-875-2245
>>> *********************************************************************
>>>
>>>
>>> —–Original Message—–
>>> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On
>>> Behalf Of Alex Clay
>>> Sent: Tuesday, September 26, 2017 5:19 PM
>>> To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
>>> Subject: Re: New Macs – Unzip Omnis
>>>
>>> Hi Michael,
>>>
>>> I’ve always setup my deployment as I want it to install, then built the installer from that. So if you setup something like this:
>>>
>>> ~/Documents/ClienTrax Installer/ClientTrax/*.lbs
>>> ~/Documents/ClienTrax
>>> Installer/ClientTrax/OmnisRT.aps/Comntents/MacOS/xcomp/*.u_xcomp
>>>
>>> You can then set the source on your installer to ~/Documents/ClienTrax Installer/ClientTrax with the destination as the Applications folder.
>>>
>>> I’m using ~/Documents/ClienTrax Installer as an example – you can store this wherever your like and it doesn’t have to be /Applications, which is handy for testing.
>>>
>>> Alex
>>>
>>>
>>>> On Sep 26, 2017, at 17:11, Michael Mantkowski <michaelj@clientrax.com> wrote:
>>>>
>>>> To all those that have used Packages as an installer for the Mac.
>>>>
>>>> I have been testing with it and it works fine for updating my Library files or creating a Full Install Package.
>>>>
>>>> But I cannot seem to figure out how to get it to update some XCOMP files that are located within the OmnisRT file.
>>>>
>>>> I have selected the ones I want via Add Files. They are added Payload with the proper Source location. But the Destination location is always showing the root ClienTrax Folder where the library files need to go. I can’t seem to find a way to change the Destination location of the three XCOMPS I want so they can be placed in the existing OmnisRT which also is in the root ClienTrax folder.
>>>>
>>>> It is acting like all files can only go to a single destination.
>>>>
>>>> Root Folder: /Applications/ClienTrax <--- Library files here >>>>
>>>> XCOMP Folder: /Applications/ClienTrax/OmnisRT.aps/Comntents/MacOS/xcomp <---- XCOMP files here >>>>
>>>> Does anyone know how I can change the Destination of the xcomps so that I can get them where they need to go?
>>>>
>>>> ********************************************************************
>>>> *
>>>> Michael Mantkowski
>>>> ClienTrax Software
>>>> 1-614-875-2245
>>>> ********************************************************************
>>>> *
>>>>
>>>>
>>>> —–Original Message—–
>>>> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com]
>>>> On Behalf Of Phil (OmnisList)
>>>> Sent: Monday, June 26, 2017 4:56 AM
>>>> To: omnisdev-en@lists.omnis-dev.com
>>>> Subject: Re: New Macs – Unzip Omnis
>>>>
>>>> Just to add my 2 cents, yep, we also use Packages for Mac, and NSIS for windows, both are excellent free systems.
>>>>
>>>>
>>>> regards
>>>> Phil Potter
>>>> Based in Chester in the UK.
>>>>
>>>> On 24/06/2017 16:30, Mirko Pepa wrote:
>>>>> Hi Mike
>>>>>
>>>>> We use NSIS in windows. Its also free.
>>>>>
>>>>> Freundliche Grüsse
>>>>> Mirko
>>>>>
>>>>> ———————————–
>>>>> Mirko Pepa, Profile GmbH
>>>>> Schaffhauserstr. 103
>>>>> 8400 Winterthur
>>>>> Tel. +41 52 213 63 33
>>>>> www.profile.ch www.helper.ch
>>>>> ———————————–
>>>>>
>>>>>
>>>>>> Am 24.06.2017 um 16:12 schrieb Bo Carleö <bo@corbisoft.com>:
>>>>>>
>>>>>> Hi Mike
>>>>>>
>>>>>> On Windows I use Installmate from Tarma software.
>>>>>> Not free but unexpensive.
>>>>>> Excellent installer app.
>>>>>>
>>>>>> Bo
>>>>>>
>>>>>>
>>>>>> På 24 juni 2017 kl. 15:43:43, Mike Matthews (omnis@lineal.co.uk) skrev:
>>>>>>
>>>>>> That sounds great. Does Windows have an equivalent, as I know we will have the similar issues there with the incorrect setup of Visual Studio.
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>> Mike Matthews, Managing Director, Lineal Software Solutions Ltd
>>>>>>
>>>>>> Apple Reseller, Microsoft Partner, SQLWorks Business Partner
>>>>>> phone: 01271 375999 | web: lineal.co.uk <www.lineal.co.uk/>
>>>>>> |
>>>>>> email: mike.matthews@lineal.co.uk
>>>>>> <mailto:mike.matthews@lineal.co.uk>
>>>>>>> On 24 Jun 2017, at 14:39, Alain Stouder Omnis <omnis@smartway.ch> wrote:
>>>>>>>
>>>>>>> Hi Michael,
>>>>>>>
>>>>>>> We use Packages too. The only thing that doesn’t work on Sierra is that you need to sign the package via a script. The next version of Package will support codesigning on Sierra as it did in older os versions.
>>>>>>>
>>>>>>> Just my 2 centimes,
>>>>>>> Alain
>>>>>>>
>>>>>>> —
>>>>>>> Learn something new every day!
>>>>>>>
>>>>>>>> On 24 Jun 2017, at 15:20, Doug Easterbrook <doug@artsman.com> wrote:
>>>>>>>>
>>>>>>>> hi Michael.
>>>>>>>>
>>>>>>>> installer programs are NOT expensive. In fact a perfectly serviceable one called ‘packages’ is free.
>>>>>>>>
>>>>>>>> s.sudre.free.fr/Software/Packages/about.html
>>>>>>>>
>>>>>>>> there is a number of posts about this in omnis list. I’ve commented one from Ale Clay that put me on to — and I’m really grateful that he did. it has links to resources which also allow code signing of the package (we have not done that part yet).
>>>>>>>>
>>>>>>>>
>>>>>>>> Alex put a sample of how to use packages on github which I used as a baseline to translate my existing installer vise setup over to packages. It took me a couple of days to get the installer vise code working in the equivalent command line as packages — but I have never looked back. Its slick and lets me do things like save serial numbers, convert/upgrade an older omnis install (say studio 4 to studio 5 or 5 to 5.1) by automatically changing serial numbers, basically anything is possible.
>>>>>>>>
>>>>>>>> github.com/barkingfoodog/omnis-pkg
>>>>>>>>
>>>>>>>>
>>>>>>>> I even used it top wrap our own stuff around the enterprizedb Postgres installer, including setting initial user accounts, uploading a database, upgrading postgres — literally, almost anything can be scripted. I’m now working to see if I can automatically set up custom ssl certificates into postgres so that we can always do TLS 1.2 connections.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> the point — packages is worth the small time investment. it
>>>>>>>> works with OSX and builds ,pkg files that apple simply
>>>>>>>> understands. (my installer can now be authenticated with
>>>>>>>> fingerprints on the new macs and I did nothing to make that
>>>>>>>> happen_
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> from alex : ……
>>>>>>>>
>>>>>>>>
>>>>>>>> Yes, we codesign the package via the command line as part of our build process. You have to export and import both your private key and the code-signing certificate to whatever machine will perform the signing. Here is an excerpt from the installer build script with some placeholders added for the dynamic bits:
>>>>>>>>
>>>>>>>> security unlock-keychain -p “[macOS password]”
>>>>>>>> productsign –sign “[your developer ID from Apple. Ours is ‘Developer ID Installer: Suran Systems, Inc.’ without single quotes]” “[temporary installer pkg]” “[final installer pkg]”
>>>>>>>>
>>>>>>>> I used these sites as resources for building this script:
>>>>>>>>
>>>>>>>> # Packages: s.sudre.free.fr/Software/Packages/about.html
>>>>>>>> <s.sudre.free.fr/Software/Packages/about.html>
>>>>>>>> # Product sign:
>>>>>>>> developer.apple.com/library/mac/documentation/Darwin/Ref
>>>>>>>> e r ence/ManPages/man1/productsign.1.html
>>>>>>>> <developer.apple.com/library/mac/documentation/Darwin/Re
>>>>>>>> f e rence/ManPages/man1/productsign.1.html>
>>>>>>>> # Signing a package:
>>>>>>>> developer.apple.com/library/mac/documentation/IDEs/Conce
>>>>>>>> p
>>>>>>>> t
>>>>>>>> ual/AppDistributionGuide/DistributingApplicationsOutside/Distrib
>>>>>>>> u
>>>>>>>> t
>>>>>>>> ingApplicationsOutside.html#//apple_ref/doc/uid/TP40012582-CH12-
>>>>>>>> S
>>>>>>>> W
>>>>>>>> 12
>>>>>>>> <developer.apple.com/library/mac/documentation/IDEs/Conc
>>>>>>>> e
>>>>>>>> p
>>>>>>>> tual/AppDistributionGuide/DistributingApplicationsOutside/Distri
>>>>>>>> b
>>>>>>>> u
>>>>>>>> tingApplicationsOutside.html#//apple_ref/doc/uid/TP40012582-CH12
>>>>>>>> –
>>>>>>>> S
>>>>>>>> W12> # osdir.com/ml/installer-dev/2010-12/msg00050.html
>>>>>>>> <osdir.com/ml/installer-dev/2010-12/msg00050.html>
>>>>>>>>
>>>>>>>> Hope this helps!
>>>>>>>>
>>>>>>>> Alex
>>>>>>>>
>>>>>>>>
>>>>>>>> Doug Easterbrook
>>>>>>>> Arts Management Systems Ltd.
>>>>>>>> mailto:doug@artsman.com
>>>>>>>> www.artsman.com
>>>>>>>> Phone (403) 650-1978
>>>>>>>>
>>>>>>>>> On Jun 24, 2017, at 6:32 AM, Michael Mantkowski <michaelj@clientrax.com> wrote:
>>>>>>>>>
>>>>>>>>> Thanks Bas,
>>>>>>>>>
>>>>>>>>> I think this will lead me in the right direction. I did not
>>>>>>>>> know about the “quarantine” options. That would explain why
>>>>>>>>> trying to work with the “Locked” and “Read/Write” option have no effect.
>>>>>>>>>
>>>>>>>>> I will try it.
>>>>>>>>>
>>>>>>>>> I agree that the installer would be the best thing. But they
>>>>>>>>> are so expensive. I don’t sell that many Mac programs and
>>>>>>>>> really just don’t want to pay for it. : ) However, I would like the more professional workflow.
>>>>>>>>>
>>>>>>>>> Mike,
>>>>>>>>>
>>>>>>>>> Still looking at Studio 4.3.1 here. It works fine once you get
>>>>>>>>> rid of the security issues. Want to move up to Studio 8 and
>>>>>>>>> probably will do so once the next version is out of beta. I
>>>>>>>>> have already completed all the code conversion for Unicode (I think – lol) so it’s ready to move…
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Michael
>>>>>>>>>
>>>>>>>>> ***************************************************************
>>>>>>>>> *
>>>>>>>>> *
>>>>>>>>> ****
>>>>>>>>> Michael Mantkowski
>>>>>>>>> ClienTrax Software
>>>>>>>>> 1-614-875-2245
>>>>>>>>> ***************************************************************
>>>>>>>>> *
>>>>>>>>> *
>>>>>>>>> ****
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> —–Original Message—–
>>>>>>>>> From: omnisdev-en
>>>>>>>>> [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On Behalf Of
>>>>>>>>> Bastiaan Olij
>>>>>>>>> Sent: Friday, June 23, 2017 8:22 PM
>>>>>>>>> To: omnisdev-en@lists.omnis-dev.com
>>>>>>>>> Subject: Re: New Macs – Unzip Omnis
>>>>>>>>>
>>>>>>>>> Hey Michael,
>>>>>>>>>
>>>>>>>>> This could be due to quarantining files. This is part of the
>>>>>>>>> gatekeeper mechanism introduces in 10.9 and slowly becoming more and more stricter.
>>>>>>>>> As downloading executables is the main vector for trojans and
>>>>>>>>> virusses and stuff to be installed on peoples computers Apple
>>>>>>>>> is doing their bit to combat this menace.
>>>>>>>>>
>>>>>>>>> Whenever you download a zip file from the internet it gets earmarked.
>>>>>>>>> Whenever you unzip that zipfile any executable files get marked
>>>>>>>>> as quarantined.
>>>>>>>>> If an application is properly code signed, and the OS can thus
>>>>>>>>> validate that the application you just downloaded is sound and
>>>>>>>>> safe, the quarantine mark is cleared and your application runs.
>>>>>>>>> It is possible only parts of the app bundle get cleared, it all
>>>>>>>>> depends on what the modifications to the app bundle are since
>>>>>>>>> it was code signed (I do believe Omnis code signs the base application).
>>>>>>>>>
>>>>>>>>> If this is indeed the case the best way is to use installers
>>>>>>>>> instead of zip files, we use bitrock and then code sign the
>>>>>>>>> installer itself. Mac OS X trusts the installer and therefor trusts whatever it installs.
>>>>>>>>>
>>>>>>>>> You can however manually clear these earmarks (attributes) with
>>>>>>>>> the xattr command.
>>>>>>>>> Open up terminal and execute:
>>>>>>>>> xattr yourapp.app
>>>>>>>>>
>>>>>>>>> I think there is a recursive option in that command that allows
>>>>>>>>> you to see if files within the app building have their own
>>>>>>>>> attributes. Note that many attributes are harmless or even
>>>>>>>>> useful but the one to look out for is com.apple.quarantine
>>>>>>>>>
>>>>>>>>> You can clear an attribute with:
>>>>>>>>> xattr -d com.apple.quarantine yourapp.app Again use the
>>>>>>>>> recursive option (probably -r) to clear out the attribute from files held within.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>>
>>>>>>>>> Bas
>>>>>>>>>
>>>>>>>>>> On 24/6/17 6:39 am, Michael Mantkowski wrote:
>>>>>>>>>> For 20 years we installed our Omnis product on the Mac by
>>>>>>>>>> Zipping Up a
>>>>>>>>> complete folder containing our product and unzipping it into
>>>>>>>>> the Applications Folder of a Mac Computer.
>>>>>>>>>> The newest version of Mac OS however seems to be locking the
>>>>>>>>>> files in some
>>>>>>>>> way when they are Unzipped so that Omnis will not run. Get a
>>>>>>>>> few errors about how it cannot access the icon files and things
>>>>>>>>> like that and then it shuts down. I have tried resetting read
>>>>>>>>> write status of the folder and files individually and cannot
>>>>>>>>> seem to get it to work. I am not even sure what it thinks is wrong.
>>>>>>>>>> What we have had to resort to is unzipping the program on an
>>>>>>>>>> older OS
>>>>>>>>> version and then copying it directly over the network to the
>>>>>>>>> local computer or using a flash drive to move it. It then works fine.
>>>>>>>>>> Does anyone know what the unzip process is doing that could
>>>>>>>>>> account for
>>>>>>>>> this?
>>>>>>>>>> **************************************************************
>>>>>>>>>> *
>>>>>>>>>> *
>>>>>>>>>> *****
>>>>>>>>>> Michael Mantkowski
>>>>>>>>>> ClienTrax Software
>>>>>>>>>> 1-614-875-2245
>>>>>>>>>> **************************************************************
>>>>>>>>>> *
>>>>>>>>>> *
>>>>>>>>>> *****
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _____________________________________________________________
>>>>>>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> —
>>>>>>>>> Kindest Regards,
>>>>>>>>>
>>>>>>>>> Bastiaan Olij
>>>>>>>>> e-mail: bastiaan@basenlily.me
>>>>>>>>> web: www.basenlily.me
>>>>>>>>> Skype: Mux213
>>>>>>>>> www.linkedin.com/in/bastiaanolij
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _____________________________________________________________
>>>>>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _____________________________________________________________
>>>>>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>>>>> _____________________________________________________________
>>>>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>>>>
>>>>>>> _____________________________________________________________
>>>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>>> _____________________________________________________________
>>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>>> _____________________________________________________________
>>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>>
>>>>> _____________________________________________________________
>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>> _____________________________________________________________
>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>
>>>> _____________________________________________________________
>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>
>>> _____________________________________________________________
>>> Manage your list subscriptions at lists.omnis-dev.com
>>>
>>> _____________________________________________________________
>>> Manage your list subscriptions at lists.omnis-dev.com
>>
>> _____________________________________________________________
>> Manage your list subscriptions at lists.omnis-dev.com
>>
>> _____________________________________________________________
>> Manage your list subscriptions at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com

_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com

New Macs – Unzip Omnis