Re: [Camelbones-devel] Framework-embedded Perl - what can be left out?

[Sherm P. <she...@gm...>]

On Mon, Dec 13, 2010 at 8:56 AM, Sherm Pendley <she...@gm...> wrote:
>
> Another option would be to include a shell script build phase in app
> templates, that copied all of the useful core files by default, and a
> main.pl that included the above scheme to report "unbundled" files.
> Simply removing (or commenting) the default shell script would then
> generate a list of modules that were actually used by the app.

Thinking this through a bit more, I like this option. Including the
Perl modules in the framework would bulk up the developer package for
no good reason. They're going to get copied into the .app bundle one
way or another, either as part of the framework or in a separate build
phase, so nothing is gained by keeping an extra copy of them around.

What's more, copying the modules as part of the framework, only to
immediately delete some of them, would be wasteful. It would also be a
potential source of errors, as the build phase that removed unneeded
modules could only be run *after* the copy files build phase that
copied the framework. If the modules are simply copied into the .app
bundle, it wouldn't matter if that happens before or after the
framework is copied.

sherm--

-- 
Cocoa programming in Perl:
http://camelbones.sourceforge.net