Re: Working with forks

On Sep 9, 2023, at 10:34, Graham Perrin <grahamperrin@gmail.com> wrote:

> On 08/09/2023 05:37, Warner Losh wrote:
> 
>> … I also never have a /usr/src on any of my systems. …
> 
> I learnt to restrict myself to /usr/doc, /usr/ports, and /usr/src after long ago confusion about where things normally reside.
> 
> The 'git -C' habit sort of forces me to think twice about which tree I am (or should be) working with before entering any command.
> 

I prefer to submit kernel problems based on having reproduced an
issue via use of, say, an official snapshot build's kernel when
I can. I reserve /usr/src/ for having such a snapshot's source
code where the snapshot's debug information expects it to be. The
/usr/src/ is not populated via git for this but via extracting
from files obtained via matches to the pattern:

http://ftp3.freebsd.org/pub/FreeBSD/snapshots/*/15.0-CURRENT/src.txz

/usr/src/ is empty unless I'm dealing with such snapshot testing
at the time.

For my own builds I have and use a worktree /usr/main-src for
main [so: 15] activity, for example. So the debug information
for my own builds does not reference /usr/src/ .

As part of this way of working I use git -C all the time. The
habit was established back when I was actively also building
and installing stable/13 and releng/13.? in addition to main.
I've kept the conventions's general structure, such that the
pattern for stable/ and releng/ based activity is still known.

===
Mark Millard
marklmi at yahoo.com