0.1.2 Mac installer problem

1 view
Skip to first unread message

Nicolas Alvarez

unread,
Oct 21, 2009, 4:54:43 PM10/21/09
to synecdo...@googlegroups.com
Michael Tughan released a 0.1.2 RC Mac installer last month. But it didn't
work if 0.1.1 was already installed. It didn't actually upgrade, leaving
the old Synecdoche 0.1.1 files.

Along with some Windows problems (that are now fixed), this totally blocked
our 0.1.2 release.

Today, I found the problem. The new installer *does* upgrade. It's just
Finder isn't noticing the version change.

- Install 0.1.1. See Synecdoche.app in Finder. It says 0.1.1 r902.
- Run the app. It's 0.1.1.
- Install 0.1.2. See Synecdoche.app in Finder. It still says 0.1.1 r902.
- Run the app. It's 0.1.2, both core client and manager, so it *did*
upgrade.
- Logout, login. Finder now shows 0.1.2 correctly!

Running "touch" on the Synecdoche.app directory instead of logout/login
also works. So a good workaround is doing 'touch' in a postinstall script in
the 0.1.2 installer.


By the way, I really think it would make things much easier if we had a
single .pkg, instead of an .mpkg.

It makes no sense for someone to install the screensaver and/or the data but
not the app. It makes no sense to install the app but not the data
directory. And while someone may not want to use the screensaver, there is
no harm in installing it anyway (as long as it's not automatically set as
the current screensaver).

So why have multiple packages at all? I think it would be better to have a
single Synecdoche-0.1.2.pkg that installs everything.

However, if we decide to do this change, it'll have to wait for 0.1.3
at least. 0.1.2 is already delayed enough.


Michael Tughan

unread,
Oct 21, 2009, 4:59:49 PM10/21/09
to synecdo...@googlegroups.com
Well, in regards to multiple packages, I've already modified the trunk
packages so that the app and the data dir are installed together. The
screensaver is still optional. Also, it's impossible to not install
the main app because I've marked it required. I think that solution
isn't bad, but I'm open to reasoning, considering the screensaver
isn't that big anyway.

Michael Tughan

Reply all
Reply to author
Forward
0 new messages