Subject: Re: pkg/26211 (Darwin bootstrap: case-sensitive HFS+ can be used)
To: None <,,>
From: Jim Bernard <>
List: pkgsrc-bugs
Date: 10/05/2006 20:00:07
The following reply was made to PR pkg/26211; it has been noted by GNATS.

From: Jim Bernard <>
Subject: Re: pkg/26211 (Darwin bootstrap: case-sensitive HFS+ can be used)
Date: Thu, 5 Oct 2006 11:41:15 -0600

 On Thu, Oct 05, 2006 at 04:41:54PM +0000, wrote:
 > Synopsis: Darwin bootstrap: case-sensitive HFS+ can be used
 > State-Changed-From-To: open->feedback
 > State-Changed-By:
 > State-Changed-When: Thu, 05 Oct 2006 16:41:53 +0000
 > State-Changed-Why:
 > Both README.Darwin and the pkgsrc guide contain references to
 > case-sensitive HFS+. Does this answer this PR?
   The guide looks good, but I still see this issue: README.Darwin adds the
 case-sensitive HFS+ option as an afterthought, rather than integrating it
 into the discussion along with UFS.  The guide discusses them together as
 comparable alternatives, which is just right.  You could say that
 README.Darwin is so short that it really doesn't matter, but that also makes
 it easy to fix.
   It would be nice to update README.MacOSX (which discusses the situation
 as of version 10.2) with mention of it, too, but unless somebody has
 a machine with a recent version on which they can test it, it will be
 difficult to make an authoritative statement.  Unfortunately, I can't
 help with that.  So, if you want to make a small change to README.Darwin
 and close the PR, I'll be content with that.
   I'll suggest this text as a replacement for the last two paragraphs of
   Note: if you already have a case-sensitive file system (either UFS or
   case-sensitive HFS+, also called HFSX and available in Darwin 7.0
   and newer) or have a spare partition that you can format with such a
   file system, you are better off using that instead of the disk image.
   It'll be somewhat faster and will mount automatically at boot time.
   You cannot use a case-insensitive (the default) HFS+ file system for
   pkgsrc, because it currently depends on case distinctions in file names.