Re: Dump commands

Am 15.08.26 um 13:22 schrieb Pocket ([email protected] via
lfs-support Mailing List):
> 
> 
> On 8/15/26 06:26, Rainer Fiebig ([email protected] via lfs-support Mailing
> List) wrote:
>> Am 15.08.26 um 00:12 schrieb Pocket ([email protected] via
>> lfs-support Mailing List):
>>>
>>
>> [ snip ]
>>> I will know for sure when I build my next release.
>>> That will be a bit into the future as I need to create and image for the
>>> version I just completed, built on a raspberry pi 5 and boot and test it
>>> on a raspberry pi 4.
>>
>> Interesting.  Would you mind telling us the SBU for your "pi 5"?  Thanks.
>>
>> Rainer
>>
>>
> 
> I don't do the SBU as I don't really care about them.

That's a pity.  I was really curious.

> The build takes what the build takes.

On a raspberry this must be an exercise in patience.  So I guess you pay
great attention to the correctness of your scripts. ;)

> 
> The raspberry pi 5 that I am using has 16GB of ram and I connect various
> drives thru the USB ports.
> 
> It take me a couple of days to do a build because I do a step at at time
> and I review each step/package before I go on to the next. Athough I
> could "just let them run".
> 
> This new "build system" I use has worked very well. I dump the commands
> from the book then run them(source) from my scripts.  One for each
> chapter.  I look over the "stock" script from the dump commands in the
> book make file, then sed the script if it requires changes, which I do
> in a case statement ;)

I'm not against case-statements, I use them, too. ;)

> 
> For example
> 
> for i in "${scripts[@]}";do
>     if test -e "$Logs"/"$i";then
>         printf "%+23s %s\n" "Skipping:" "$i"
>         continue
>     else
>         printf "%+23s %s\n" "Building:" "$i"
>     fi
> 
> [putolin]
> 
> case "${i##*[0-9]-}" in
>     pkgmgt) continue;;        #    Not needed
>     man-pages) ;;
>     iana-etc) ;;
>     glibc)
>         sed -i '/^patch/s/^/#/' -i "$Build/$i"
>         sed -i '/^make check/s/^/#/' -i "$Build/$i"
>         sed -i '/^grep/s/^/#/' -i "$Build/$i"
>         sed -i '/^rm/s/^/#/' -i "$Build/$i"
>         sed -i '/^systemctl/s/^/#/' -i "$Build/$i"
>         sed -i '/^make DESTDIR/s/^/#/' -i "$Build/$i"
>         sed -i '/^install -vm755 dest/s/^/#/' -i "$Build/$i"
>         sed -i '/DIR/s/^/#/' -i "$Build/$i"
>         sed -i '/^localedef/s/^/#/' -i "$Build/$i"
>         sed -i '/^make localedata/s/^/#/' -i "$Build/$i"
>         url=$(_get_pkg_url "$Build/url-list.text" "tzdata2025c")
>         _fetch_pkg "$url" "$Sources"
>         _copy_archive "$Sources" "$Build" "$url"
>         sed -i '/^tzselect/s/^/#/' -i "$Build/$i"
>         sed  -e '/^ln/s|\*\*EDITME<xxx>EDITME\*\*|EST5EDT|' -i
> "$Build"/"$i"
>         sed  -e '/^#localedef -i C /s|#localedef|localedef|' -i
> "$Build"/"$i"
>         sed  -e '/^#localedef -i en_US/s|#localedef|localedef|' -i
> "$Build"/"$i"
>         ;;
>     zlib)
>         sed -i '/^make check/s/^/#/' -i "$Build/$i"
>         ;;
> 
> [putolin]

Thanks.  But enlighten me: what is "putolin"?  I found a lot of stuff
relating to motor oil.  But I don't think that you use that to make your
scripts run smoother or faster?

Rainer

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-support
Unsubscribe: See the above information page