Mac installer
Nicolas Alvarez
How does the "new" Mac installer work? Having a Mac, Xcode, and Iceberg,
how do I make an installer like our current 0.1.1 release?
Why was WhiteBox's Iceberg chosen over the standard PackageMaker tool
bundled with Xcode?
Can an installer be built from the command line, without access to a GUI?
Is there support for localization of installer text? Would each language be
a different *source* file, or is all text in the same file? The former
would be easier for translators. (by "source file" I mean something that
would be checked into SVN; if it's all in the same file and then Iceberg
splits it into a file per language when building the .pkg, it doesn't
count)
David Barnard
Alvarez<nicolas...@gmail.com> wrote:
>
> We need internal / development documentation as much as user documentation.
I was thinking exactly this. In fact, I had a few notes for the
Windows installer in mind.
Particularly, I wanted to hammer out the user experience
Do you want to use gobby?
Michael Tughan
>
> We need internal / development documentation as much as user
> documentation.
>
> How does the "new" Mac installer work? Having a Mac, Xcode, and
> Iceberg,
> how do I make an installer like our current 0.1.1 release?
Iceberg uses the paths for the Deploy_noSandbox build right now, as
that's the typical build I figure we'll be using for release. To build
a release, build the Deploy_noSandbox target using Xcode, then open
the Iceberg project file and build it. It'll place the built package
(or multi-package) in the build subdirectory, which can then be zipped
or tarred up and distributed.
>
> Why was WhiteBox's Iceberg chosen over the standard PackageMaker tool
> bundled with Xcode?
Because I was recommended Iceberg over PackageMaker for a feature I
was looking for (I don't remember what it was now).
>
> Can an installer be built from the command line, without access to a
> GUI?
Not as far as I know, but I'll look into it.
>
> Is there support for localization of installer text? Would each
> language be
> a different *source* file, or is all text in the same file? The former
> would be easier for translators. (by "source file" I mean something
> that
> would be checked into SVN; if it's all in the same file and then
> Iceberg
> splits it into a file per language when building the .pkg, it doesn't
> count)
The former. I can set up the Installer texts for localizations, which
I believe will put them into separate <language>.lproj folders, which
will then be used as appropriate by Installer.app.
>
>
Michael Tughan
Michael Tughan
I'll move the English language files to an English folder, and we can
add other folders for other languages later on if we add them.
Michael Tughan
Nicolas Alvarez
> Do you want to use gobby?
Yes, I prefer it to web apps (etherpad). It has syntax highlighting too.
I have a server running at stuff.povaddict.com.ar. Note that only
gobby 0.4.92 will work; there is protocol incompatibility with previous
versions.
Nicolas Alvarez
> David Barnard wrote:
>> Do you want to use gobby?
>
> Yes, I prefer it to web apps (etherpad). It has syntax highlighting too.
Of course, feel free to put your current notes directly in the wiki :)