Re: Git haas gone wild (Rust)

On 9/8/2025 15:15, Vadim Goncharov wrote:
> On Sat, 6 Sep 2025 13:37:22 -0500
> Kyle Evans<kevans@FreeBSD.org> wrote:
>
>> On 9/6/25 08:47, Warner Losh wrote:
>>>
>>> On Sat, Sep 6, 2025, 7:39 AM Eugene Grosbein <eugen@grosbein.net
>>> <mailto:eugen@grosbein.net>> wrote:
>>>
>>>      06.09.2025 20:17, Matthias Andree wrote:
>>>    
>>>       > Am 05.09.25 um 18:42 schrieb Michael Osipov:
>>>       >> Folks,
>>>       >>
>>>       >> you might want to enjoy or discuss:https://lore.kernel.org/
>>>       >><https://lore.kernel.org/>
>>>       >>git/20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks.im/T/#t
>>>       >><http://20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks.im/T/#t>
>>>       >>
>>>       >> Michael
>>>       >
>>>       > This poses a bootstrapping problem, (if we need Git to get the Rust
>>>       > build for ports... there's a chicken-and-egg problem)
>>>
>>>      Maybe it is time for us to bring net/gitup into base system.
>>>      It's written in pure C and comes under BSD2CLAUSE license.
>>>      Also, it matured over many years and runs just fine.
>>>
>>>      For the reference:https://github.com/johnmehr/gitup
>>> <https://github.com/johnmehr/gitup>
>>>
>>>
>>>
>>> Got is better supported and wouldn't be an instant burden.
>>>
>>> Warner
>>>
>>>    
>> fuz@ and I discussed this a little bit yesterday, too.  I think it'd be fine
>> to introduce got if we have a simple wrapper to checkout (and maybe update)
>> a repository in a git-compatible way so that one could easily migrate
>> between the two.  Something like: clone the repository to
>> /usr/{src,ports}.git, checkout a worktree to /usr/{src,ports}, then add a
>> git-style .git symlink to point back to the appropriate .git dir so that git
>> recognizes it as a worktree.
>>
>> git itself can create an identical layout with `git clone
>> --separate-git-dir=/usr/src.git ...`
> Will it support multiple worktree`s? I use several checkouts of /usr/ports in
> different jails with different branches, but same .git

This is also a concern for my use case as I support multiple 
architectures at present (AMD64 and both ARM64 and 32) and typically 
have four worktrees out at any given time (three typically under 
"-stable" and one that fluctuates while I'm testing things, such as 15- 
right now) some of which I then build under Crochet as nanobsd is broken 
(and I haven't bothered to fix it although I probably could) for some of 
my "embedded" ARM targets.

My use of it is not in /usr/ports; it is the base system source (/usr/src)

-- 
Karl Denninger
karl@denninger.net
/The Market Ticker/
/[S/MIME encrypted email preferred]/