(5)
Your rating: Now say why...
- Download Now
4.8 MB -
Visit Developer's Site
Stephane Sudre
Iceberg is an Integrated Packaging Environment (IPE) that allows you to create packages or metapackages conforming to the Mac OS X specifications. With Iceberg, you can quickly create your installation packages using a graphic user interface similar to your favorite development tools. Iceberg can also be useful for Administrators who want to gather in a metapackage numerous packages for remote distribution via Apple Remote Desktop.
What's New
Version 1.2.9:
- Fixed an issue with the Directory Services code used to retrieve the list of group IDs.
Requirements
PPC / Intel, Mac OS X 10.2 or later.
PPC / Intel, Mac OS X 10.2 or later.
Iceberg User Discussion (Write a Review)
Overall:
(5)
(5)
| Downloads:18,955 |
| Version Downloads:5,525 |
| Type:Development : Compilers |
| License:Free |
| Date:16 Mar 2010 |
| Platform:PPC / Intel |
| Price:Free |
Overall (Version 1.x):  |
| Features: |
| Ease of Use: |
| Value: |
| Stability: |
-
-
-
Iceberg is an Integrated Packaging Environment (IPE) that allows you to create packages or metapackages conforming to the Mac OS X specifications. With Iceberg, you can quickly create your installation packages using a graphic user interface similar to your favorite development tools. Iceberg can also be useful for Administrators who want to gather in a metapackage numerous packages for remote distribution via Apple Remote Desktop.
Copyright © 2012 MacUpdate LLC
- -
-2
+6
+2
These components are used to build the packages.
> Additionally, why does this installer write data to /usr (/usr/local/bin/freeze and /usr/local/bin/goldin)?
These are command line tools. Check the documentation chapter "Frequently Asked Questions" to get more information about the freeze command line utility. goldin is a command line tool used to split forks.
> And why is there no mention that this installer will litter my drive with data beyond what an application uninstaller could find?
Check the documentation chapter "Installing Iceberg", installation blueprints are provided explaining what is installed where. Additionally, an uninstall script is provided.
+56
donmontalvo reviewed on 15 Mar 2009
Don Montalvo
+3
+70
Cerniuk reviewed on 08 Oct 2008
This is what Packagemaker should have been. Don't read, just download, install and smile because your installer falderal is over.
Easy to use, covers the silly manual parts that PackageMaker forces you into, flexible, compatible and definitely worth paying for... but free!
However, the download host used for this is TERRIBLE. I have yet to be able to successfully download 1.2. Mirror it somewhere else >_
+1
+322
+1
+322
+1
+322
The above link is the download link posted here on the MacUpdate product page for Iceberg and it downloads version 1.2.1 beyond any doubt or question. I uploaded the file myself, just for you, because you posted that you could not download the file from the developer's server. Well, I did downlooad it from the developer's server with no issues whatsoever and verified the version number and then uploaded it to the MacUpdate servers, and then I downloaded it again (this time from the MacUpdate server) and the image mounted just fine and is version 1.2.1.
http://www.macupdate.com/~matt/devel/info.php/id/14516
Check that link, it's messed up somehow. I haven't had any other problems on macupdate, so this seems odd.
-1
Anonymous reviewed on 02 May 2005
- why don't use /usr/local/bin instead of /usr/bin?
- why an always-running root daemon when I create a package once a week? I think it's much better to enter my admin password in case root privileges are needed to create a package.
- for the same reason mentioned above, why a StartupItem when the daemon could be launched only when needed?
If all applications should have their own daemon and StartupItem our Macs would become slow as a PC running Windows :-)
Consider the previous points as suggestions, not critics, I understand that the developer has built and published Iceberg for free, thus I greatly appreciate his effort.
Regarding the StartupItem and always running Daemons, it's just that on 10.2, there is no real other solutions.
In the future, the OS requirements will be 10.4 (because of this x86 thing) and this will be handled differently then.
+3
Traditionally for unix admins, /opt has been preferred. Unfortunately I was overuled with Growl, but either should be acceptable. This makes it so that iceberg isn't in the default installation directories. 3rd party tools being kept in a separate directory is rather nice for management :)
Since you plan to build the next major release of Iceberg only for Tiger take a look at its new launchd daemon (if you have not yet done this), I think it's just what you need.
Anonymous reviewed on 20 Feb 2005
If you're a thrill seeker, you can force quit Installer.app during this step. But you would do it at your own risk.
The Optimization Step is a standard procedure of any installation performed by Installer.app. So if you think this should be improved, you will need to contact Apple via a feedback form or a Bug Report.
My $0.02
I also don't like much when I'm forced to restart just because a daemon has to be launched.
( but I like iceberg anyway ;-) )
+1
For the restart, I have some plan to improve this.
+2
+2
+4
Cabbage reviewed on 19 May 2004
"Ever since I started creating packages with PackageMaker, I have been hoping somebody would create a utility like this"
and of course I'm not making Package's anymore. You know how much time this would have saved me? I always had to login as root just to get my package's perfect with permissions. Now I can edit them right in the app like StuffIt and VISE installer.
Note to Apple - Kill Package maker in Tiger and replace it with Iceberg
What is the point of the daemon that is always running? You gotta lose that. It should only be run when a package is getting built and then killed. No reason to have it running 24x7.
If you're thinking about anythng for future released get some simple stuff in the for the pre and postflight scripts so I don't have to be editing shell scripts all the time.
+1
Anonymous reviewed on 22 Mar 2004
My installer is somewhat complex - it has a number of packages and a metapackage. This is a major pain to deal with in PackageMaker. I am always having to open up the .plists of my packages and tweak things after every build.
Tweak no more! Iceberg is going to save me a ton of time! And it is free!
Anonymous reviewed on 22 Mar 2004
However, I really wish Iceberg didn't install a StartupItem. It seems silly to have a background daemon running all the time when I might only run Iceberg once or twice a month. I understand that this architecture has its advantages, but I'm going to stick with PackageMaker until Iceberg loses the background process.
Also, Iceberg's install package puts files in several places on the filesystem. Software that's written this way should also include a way to uninstall the scattered pieces. I didn't see a way to remove Iceberg without manually tracking down and deleting the various components. On the plus side, at least the location of the components are clearly diagrammed on the Iceberg site.
The uninstall tool is a good idea. I will add it on my to-do list.
Yoursort rated on 30 Jan 2012