• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Does Installer.app rely on some tricks to merge data & resource forks?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Does Installer.app rely on some tricks to merge data & resource forks?


  • Subject: Re: Does Installer.app rely on some tricks to merge data & resource forks?
  • From: Peter Bierman <email@hidden>
  • Date: Mon, 26 Feb 2007 11:19:41 -0800

At 11:39 PM +0100 2/24/07, Stéphane Sudre wrote:
4. When I build the same package with a shell script using command line tools including pax, the produced package is exactly the same as seen from the outside:

So it makes one wonder what's the difference between a pax archive produced by /bin/pax and one produced by the BOM Framework (if we put aside the fact that /bin/pax is not ACL compatible when the other solution is).


I don't know why they're different, but try using 'ditto -c' to create your archive instead of pax.

'ditto' is the command line interface to the BOM framework.

-pmb
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Does Installer.app rely on some tricks to merge data & resource forks? (From: Stéphane Sudre <email@hidden>)

  • Prev by Date: Does Installer.app rely on some tricks to merge data & resource forks?
  • Next by Date: Best way to require 10.3.9 or later to install
  • Previous by thread: Does Installer.app rely on some tricks to merge data & resource forks?
  • Next by thread: Best way to require 10.3.9 or later to install
  • Index(es):
    • Date
    • Thread