NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkgsrc build server



mayuresh%acm.org@localhost (Mayuresh) writes:

>On Sat, Jul 04, 2020 at 09:49:32PM -0400, Greg Troxel wrote:
>> >> I would say: don't ever use make update.
>> > Why does something exist that isn't to be used `ever'?
>> You seeme to have conflated "I would say" and "everyone woudl say".

>It's worthwhile to explain why even you'd say and my question is merely a
>hint to provoke an insightful answer.


The update process is pretty brittle. Updates may fail, due to
broken packages, unresolved dependencies or due to local errors.
Since updates work by recursively deleting, building and re-adding
things, you'll end with a system were possibly many packages have
been deleted and that cannot be added simply again.



>> I think the notion that replace is risky and update is not is confused.

>Depends on how you define the risk.

>replace can lead to packages that are alive (installed) but inconsistent
>with each other [would exist but won't possibly run]
>update can lead to packages getting wiped out *if* there are build errors.


Yes. But the damage from update is usually much larger and not
easily recoverable unless you have the old pkgsrc tree (and distfiles)
available somewhere.



>To me there is no value in having a package installed but not functioning
>- giving me a just a false feel of safety of its existence.

>Also, if I am doing a compilation on non-prod build server wipe out is no
>risk IMO.

>I'd use replace when I know exactly what I am doing and not as a default.


I neither do source updates or replaces. I build in a separate
chroot and add/update from the generated binary packages. Everything
else proved to be a waste of time. I ended too often in a situation
where I had to re-build everything (and fix a few packages in
between). It's still the same effort (in terms of computer ressources),
but it's now mostly automated.



-- 
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."


Home | Main Index | Thread Index | Old Index