Re: [MacPerl-Porters] installation thoughts

At 21:47 +0200 2001.09.17, Thomas Wegner wrote:
>You should also consider the load time of a static vs. dynamic perl binary.

Good point; however, most people launch MacPerl and leave it open, so that
is a lesser consideration for MacPerl app users, I think.

However, it just goes to show that probably some will want static, some
dynamic (of course, all PPC builds will have dynamic loading, just a matter
of what is statically linked in from the beginning).


>>And then there is the idea of including the SYM files and the source, so
>>people can go through the debuggers if they want to.
>
>People who like debugging will probably be able to build the sources
>themselves; after all it's not too hard to follow the build recipe. And
>SYM-files  are no lightweights, so I wouldn't include them at all.

People in the past have requested them, but that was before it was this
easy for them to build it, so you may be right.


>I personally don't like FAT binaries as I don't see their need. If I have
>a 68K
Actually, as it turns out, VISE can take the FAT binary and install either
68K, PPC, or FAT as needed.  So I might be able to just put in one binary
in the installer, and have the installer figure out which to install.


>Mac, I need the 68K binary, if I have a PPC Mac, I need the PPC binary,
>if I have both, I can get both distributions. What about separating the
>binaries by architecture (68K, PPC), where 68K is generally static, and
>PPC is generally dynamic. I don't worry about the -DDEBUGGING switch; as

If there is a significant gain to be had by having all the extensions
static on PPC, then that will have to be an option.


>you said, if there's no speed penalty, just leave it in (don't confuse
>people). Then, make the Perl library a separate package. This means,
>that the PPC app and tool should come with all needed shared libraries
>for their extension modules (i.e. the :lib:MacPPC: directory).

Yeah.


>Does that make sense (I'm a bit tired :)?

Yep.

More thoughts still welcome,

-- 
Chris Nandor                      [email protected]    http://pudge.net/
Open Source Development Network    [email protected]     http://osdn.com/