On 4/1/01 11:21 PM, "Bill Stephenson" <[EMAIL PROTECTED]> wrote:
> 
> I thought maybe the problem is that they were "Carbonized Classic Mac OS"
> applications and not truly Mac OS X "Native" apps and somehow depended on
> the HFS file structure.  As I said before, I thought it might be a stupid
> question. But something odd is going on here.
> 

As I understand it, fully carbonized apps _should_ work just fine on UFS,
but I've definitely heard of problems with them.  All the carbon libs should
be able to handle this, but that won't stop a careless programmer. :)

> I won't be running "Classic" with OS X and I figured it might be easier to
> install perl modules if I used a unix format on the disk. (any comments on
> that?). But if it doesn't make a difference when installing unix software
> and it breaks OS X apps, then it doesn't seem to make sense to use a unix
> disk format.
> 

For what its worth, in the past day or two, I have installed the following
perl libraries on a HFS+ disk without any real problems:

LWP (the entire bundle)
DBI & DBD::mysql
Time::Timezone
Sys::HostIP
Mail::Sendmail
Net::DNS
Mail::POP3Client
Net::IMAP::Simple
Net::Whois

I did have a small problem with Time::Timezone, but that complained about an
environment variable being ignored when set from %ENV - I'm pretty sure that
didn't have anything to do with HFS+.

Ian

Reply via email to