Re: [PATCH v1 1/2] docs: sphinx-pre-install: add macOS Homebrew support

[Chen Miao]

Weijie Yuan <wy@xxxxxxxxx> 于2026年8月10日周一 11:48写道：
>
> On Sun, Aug 09, 2026 at 04:34:04PM -0600, Jonathan Corbet wrote:
> > Chen Miao <chenmiao.ku@xxxxxxxxx> writes:
> >
> > > Thanks for the clarification. I'll first check whether the kernel documentation
> > > already has something like a "macOS kernel development guide." If not, I think
> > > it might be worth documenting this.
> > >
> > > In particular, macOS uses a case-insensitive APFS volume by default, which can
> > > cause unexpected problems for newcomers working with the Linux kernel source
> > > tree. It would be unfortunate if there were no documentation covering the
> > > things developers need to be aware of when doing kernel development on macOS.
> > > That said, I suspect this would be better handled in a separate patch series.
> > >
> > > Of course, if such documentation already exists, then that's even better, and
> > > there would be no need to add another one.
> >
> > There is no such guide now.
> >
> > Correct me if I'm wrong, but I *think* that absence reflects the fact
> > that Linux kernel development is mostly done on Linux systems?
>
> Yes, I think so. But while macOS is not a common platform for kernel
> development itself, it might still be worthwhile to make things a little
> easier for people who want to contribute to the kernel *documentation*
> from macOS.
>
> That said, I don't have any data on how many people would actually want
> to work on the documentation from macOS. In my own case, though, there
> have been a few times when I only had an Apple machine available and
> still needed to get some work done.
>
> So overall, if supporting that use case is not too complicated and does
> not create much of a maintenance burden, having one more option
> available does not seem like a bad thing.
>
> Thanks.
Thanks for the discussion. My takeaway is that support for macOS
*development* is still limited.

For v2, I’ll limit the change to kernel *documentation*: I’ll add a note to
how-to.rst for macOS users about APFS being case-insensitive by default
and the resulting issue. I won’t try to document a broader macOS development
setup in this series; that would need more established guidance first.

Unless there are objections, I’ll proceed on that basis for v2.

Thanks.
>
> > We can certainly add such a guide if somebody is willing to write it,
> > and if it would be useful to people.