From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Staying up-to-date
Date: Wed, 12 Jun 2024 17:55:02 -0400 [thread overview]
Message-ID: <CFD44858-EDE5-40B7-BAD1-902A5111BEBE@stanleylieber.com> (raw)
In-Reply-To: <C5891CCB-A456-4D3F-A4FB-46D8EB68F576@eigenstate.org>
On June 12, 2024 3:34:09 PM EDT, Ori Bernstein <ori@eigenstate.org> wrote:
>The rootstub script does exactly what it says on the tin: it stubs out the root dir. Basically, it compensates for git not having a good way to store empty directories. It's more or less only ever needed if we add new architectures.
>
>Another script could be added, but it's not obvious to me what it should do, and it's not at the top of my priority list to figure it out.
>
>These kinds of manual step tend to be context dependent, and are often one-off, only needed when a significant change gets made to the system. And to complicate the matter, many users have local changes to the system. It would be nice if the scripts we shipped with the system were designed to respect those local changes (though there's obviously only so much you can do).
>
>It's hard to get right. It would be nice if someone managed to do it in a simple, maintainable, and reliable way.
>
>
>On June 12, 2024 1:10:48 PM EDT, Thomas Nemeth <tnemeth@free.fr> wrote:
>>Le mercredi 12 juin 2024 15:04:59 CEST, vous avez écrit :
>>> specifically, sometimes there are some dependencies between
>>> programs or libraries that require some additonal steps to
>>> fix bootstrapping issues -- for example, a new instruction
>>> added to the compiler/linker and used in libc needs the new
>>> compilers and linkers to be installed before building the
>>> rest of the system.
>>
>> Can't the rootstub script handle that ?
>>
>>
>>
>>
>
fwiw, this was all discussed at the dawn of 9front and rejected as being too complicated to bother with. opinions may have changed, but it's good to reiterate that it's not as simple as writing a one liner.
sl
next prev parent reply other threads:[~2024-06-12 22:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 14:57 Thomas Nemeth
2024-06-11 15:08 ` phil9
2024-06-11 15:15 ` Thomas Nemeth
2024-06-12 11:57 ` cosarara
2024-06-12 16:57 ` Thomas Nemeth
2024-06-13 0:46 ` sl
2024-06-13 1:05 ` sl
2024-06-13 6:31 ` Thomas Nemeth
2024-06-13 17:16 ` hiro
2024-06-12 12:21 ` ori
2024-06-12 2:30 ` Thaddeus Woskowiak
2024-06-12 17:10 ` Thomas Nemeth
2024-06-12 12:51 ` hiro
2024-06-12 13:04 ` ori
2024-06-12 17:10 ` Thomas Nemeth
2024-06-12 19:34 ` Ori Bernstein
2024-06-12 21:55 ` Stanley Lieber [this message]
2024-06-12 17:03 ` Thomas Nemeth
2024-06-12 17:56 ` hiro
2024-06-12 18:11 ` Thomas Nemeth
2024-06-12 19:35 ` Ori Bernstein
2024-06-13 6:38 ` Thomas Nemeth
2024-06-14 20:11 ` hiro
2024-06-16 10:01 ` Thomas Nemeth
2024-06-16 13:03 ` Thaddeus Woskowiak
2024-06-16 14:27 ` Thomas Nemeth
2024-06-16 18:02 ` ori
2024-06-17 11:04 ` hiro
2024-06-16 18:00 ` ori
2024-06-16 20:20 ` [9front] Out-of-date and obsolete documentation Lyndon Nerenberg (VE7TFX/VE6BBM)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CFD44858-EDE5-40B7-BAD1-902A5111BEBE@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).