Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Use logGen for re-packaging OS X installers UNIX
The freeware command-line utility logGen is used for detecting filesystem changes after a preference change or package installation. This is primarily useful when creating your own .pkg files, so you know what you need to package. This package is o­nly compatible with OS X 10.3 and above, due to some perl modules that are missing in earlier version. This product meets an important need for enterprises that need to re-package software installs.

Using this script is very simple. Just run it once, and then install / change / remove whatever you want, and then run the script one more time. This was invaluable to me for repackaging the Windows Media Player 9 install at my company because Microsoft broke the VISE DoAutoInstall command that normally would be used to silent up an install. This has been the most important tool I've found in the past year.

72KB download (.DMG)
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (1 vote cast)

Use logGen for re-packaging OS X installers | 4 comments | Create New Account
Click here to return to the 'Use logGen for re-packaging OS X installers' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Use logGen for re-packaging OS X installers
Authored by: sapridyne on Apr 02, '04 01:01:26PM

I have used this for the past several weeks and it's great!

[ Reply to This | # ]
Use logGen for re-packaging OS X installers
Authored by: pinguru on Aug 17, '04 01:51:15PM

This is a fantastic tool. Now all we need is for some clever monkey to write a script or tool to read a LogGen output file and go collect the files up and organise them into a package-root structure. Mike Bombich? Joel Rennich, David O'Donnell?

I would do it myself, but my shell scripting sucks!

[ Reply to This | # ]
Use logGen for re-packaging OS X installers
Authored by: ljhilliii on Oct 22, '04 12:01:31PM

my first venture into Perl.. Here it goes... this will read in your change file and then create a script.. to move all the noted files/directories.

(Note you will want to change the destination directory... )

#!/usr/bin/perl -w
use strict;

print " What is the name of the Change file \n";
my $changefile =<>;
chomp $changefile;
open(INFO, $changefile) || die "could not open '$changefile' $!";
open(OUT, "> output.txt") || die "could not open output";

my @lines = <INFO>;


print " What is the name of the program you are packaging? ";

my $appname = <>;
chomp $appname;

foreach my $line (@lines) {
chomp $line;
if (-r $line) {
print OUT "ditto -V --rsrc '$line' '/Users/lhill/packages/$appname/source$line'\n";
print "ditto -V --rsrc '$line' '/Users/lhill/packages/$appname/source$line'\n";


[ Reply to This | # ]
Use logGen for re-packaging OS X installers
Authored by: bluehz on Aug 18, '04 12:56:14AM

One technique I have been using for a while now if compiling my own stuff is the following (let assume we have downloaded xyz_src.tgz and we want to compile and then create an OS X pkg from it):

tar -zxvf xzy_src.tgz
cd xyz_src.tgz
mkdir pkgbuild
sudo make install DESTDIR=$cwd/pkgbuild

The DESTDIR cause all the installed elements to be place into the pkgbuild dir you created in their proper hierarchy (e.g. usr/local/bin, usr/share/man/man3, etc). Then to build a pkg you simply use the hierarchy you created in the pkgbuild as your source for PackageMaker. The DESTDIR is recognized by about 75% of the stuff I build, but some of the source code just will not build into a different directory. Works great for the majority of stuff though.

[ Reply to This | # ]