bdist_mpkg can't do this simply yet. It's not designed as a general
package creation tool, it's designed to do what it does and little
else.
As I said, by default, PackageMaker creates mpkgs that use ".." as the
path, so you need to manually copy the packages *next to* the mpkg.
Not inside.
Sounds like that is probably it. So I should manually copy the packages
into the mpkg? What would be a simple python script to make bdist_mpkg
do that given a list of pkgs.
Thanks again,
Bob Ippolito wrote:
On Mar 7, 2005, at 11:20 AM, Bob Ippolito wrote:
On Mar 7, 2005, at 11:02 AM, Charles M
On Mar 7, 2005, at 11:20 AM, Bob Ippolito wrote:
On Mar 7, 2005, at 11:02 AM, Charles Moad wrote:
I am trying to make a mpkg using PackageMaker that includes a
combination of frameworks wrapped as pkg's, and bdist_mpkg outputs.
Each of these pkg's work fine when installed separately, but die whe
On Mar 7, 2005, at 11:02 AM, Charles Moad wrote:
I am trying to make a mpkg using PackageMaker that includes a
combination of frameworks wrapped as pkg's, and bdist_mpkg outputs.
Each of these pkg's work fine when installed separately, but die when
I try running the resulting mpkg. One machine
