Re: Etcupdate runtime has more than doubled....Why?

On 4/1/26 10:13, bob prohaska wrote:
> For some time now I've been using etcupdate on a self-hosting
> armv7 (RPi2) system. Lately, the runtime for etcupdate after
> a world/kernel update from source has seemingly more than doubled.
> It used to take less than one hour, now it's past two hours and
> not done yet. The last process is a series of c++ processes which 
> take most of the added time.
> 
> Apart from tracking -current the machine doesn't do much, but
> I didn install a /usr/ports directory recently though it's only
> been used to build named. The slowdown in etcupdate seems to
> have appeared following that change.
> 
> Might the addition of a ports tree have increased etcupdate's
> run time, and is there in any case some housecleaning that will
> speed it up?
> 
> Thanks for reading,
> 
> bob prohaska
> 
> 
> 

etcupdate has the option:


-B            Do not build generated files in a private object tree.
              Instead, reuse the generated files from a previously built
              object tree that matches the source tree.  This can be
              useful to avoid gratuitous conflicts in sendmail(8)
              configuration files when bootstrapping.  It can also be
              useful for building a tarball that matches a specific
              world build.


So, if one already has the required context, its use might be relevant.
Of course, without the proper context, it should not be used.

What was the context-status and use vs. not for -B ?


-- 
===
Mark Millard
marklmi at yahoo.com