Re: Chap 35. Updating an existing system from sources (xorg?)

[Ramiro Aceves <ea1abz%gmail.com@localhost>]

El 29/10/24 a las 11:11, Valery Ushakov escribió:
> There's really no mystique about build.sh
>
> On Mon, Oct 28, 2024 at 13:48:19 +0100, Ramiro Aceves wrote:
>
> > And with "-u" It does not compile everything but only the source
> > that has changed from the last compilation, is not it?
>
> build.sh is a convenience wrapper to build and invoke nbmake-$machine
> which is just a wrapper around make(1) that sets some variables for
> the cross-compilation.  build.sh -u in the end is (not "is like", it
> really is) just a make invocation, so all you make-related knowledge
> and intuitions apply.

Hi Uwe

Thanks for the explanation.

> You can use the nbmake-$machine manually as you would use make to
> build just a single program/library by going to the relevant directory
> in the source tree and running nbmake-$mahchine there, etc, etc.
>
>
> > And for installing:
> >
> > ./build.sh -x -j4 -O ../obj -T ../tools install=/ will install only xorg or both xorg and the system?

Yes, I have tested that and it installs both xorg and the system.


> Just unpack the X sets with something like
>
>      for f in x[!e]*.tgz; do tar -C / -zxpf $f; done
>
> That installs all X sets except xetc.tgz (use etcupdate for the
> latter).

nice to see the "low level" way of working. Great in case of a disaster 
to recover the system.

> I don't think I have _ever_ used build.sh install.  The simple mental
> model of "unpack everything except etc sets then etcupdate etc sets"
> is just so much more obvious and unobscured that I fail to see any
> need, or any advantage in hiding that behind build.sh or

I find build.sh handy as a NetBSD novice. But it depends of course what 
you are used to.

> sysutils/sysupgrade.  Besides, I usually don't have the tree around
> the target machines anyway.

Also have used that tool and works. I have to use the "low level" 
aproach just to practice.

Many thanks.
Ramiro.



> -uwe