On Tue, Jul 17, 2012 at 3:49 PM, Michael McCracken
wrote:
> That makes sense - but as you mention, it seems like there's some
> missing functionality.
I think so, yes, but it can get the job done.
> However, it's no fun if you have a lot of subpackages to add that way.
nope -- but for the most
On Wed, Jul 18, 2012 at 11:14 AM, Chris Barker wrote:
> On Tue, Jul 17, 2012 at 3:49 PM, Michael McCracken
> wrote:
>
>> That makes sense - but as you mention, it seems like there's some
>> missing functionality.
>
> I think so, yes, but it can get the job done.
>
>> However, it's no fun if you h
On 18 Jul, 2012, at 0:25, Chris Barker wrote:
>
>
> It's a big ugly, but I've managed to put packages into the zip with
> something like this:
>
> includes = ["package",
>"package.subpackage"
>"package.subpackage.module1"
>"package.subpackage.modu
On Tue, Jul 17, 2012 at 5:25 PM, Chris Barker wrote:
> On Tue, Jul 17, 2012 at 11:03 AM, Michael McCracken
>
>> My question is: why does 'packages' copy the package recursively, but
>> not into the .zip,
>
> because there are packages that don't work right if zipped -- so this
> gets around that.
On Tue, Jul 17, 2012 at 11:03 AM, Michael McCracken
> My question is: why does 'packages' copy the package recursively, but
> not into the .zip,
because there are packages that don't work right if zipped -- so this
gets around that.
> while 'includes' only gets single modules?
I suspect it's be
I am trying to package a main .app with helper apps in
Main.app/Resources/Helper.app, and I want to have a single
Resources/lib directory and a single Frameworks/ directory to cut down
on space.
So I'm tweaking the main app's includes and packages options to get
all the dependencies in one place,
