Re: package upgrade strategy

[r0ller <r0ller%freemail.hu@localhost>]

Hi All,

Thanks for all your answers (Alistair, Brad, Jeff, Jeremy)! They all seem to point in one direction i.e. to use pkgsrc with which I don't have any problem. I'm kind of used to it but I hoped that there's a way to avoid compiling relatively big programs (like seamonkey) in a case when I just want to check something out and get rid of it if it does not fit the bill. The scenario is something like that I have a 10 years old desktop for our kids (some say this word is negative for native English speakers, I'm not one of them so please, forgive) to play online flash games, watch youtube videos, etc. with 3gb ram, intel core2 conroe cpu with 1 core+igp and a conroe asrock board which all serves pretty well at their age for this purpose -at least with NetBSD;) Midori did fit the bill for everything they wanted till they bumped into codecombat which doesn't work. So I wanted to quickly check out another browser and this is exactly when I don't have time to compile anything:) As mentioned, by checking out the earlier 7.0 Q1 repo helped with seamonkey and codecombat runs fine in that but in such cases compiling each browser till I find the right one is not an option. I mean, before seamonkey I also checked out epiphany and firefox, which have the same bug as midori in that online game. Finding out that seamonkey fits the bill took roughly 15 mins, but compiling three browsers would have taken a lot more than that. Don't get me wrong, in general I agree with all your suggestions, I just hoped that there's still a way to keep different versions of pkgs in parallel.

Best regards,
r0ller

-------- Eredeti levél --------
Feladó: Alistair Crooks < agc%pkgsrc.org@localhost (Link -> mailto:agc%pkgsrc.org@localhost) >
Dátum: 2017 szeptember 28 18:20:31
Tárgy: Re: package upgrade strategy
Címzett: Jeff_W < jgw%sdf.org@localhost (Link -> mailto:jgw%sdf.org@localhost) >
 
On 28 September 2017 at 08:40, Jeff_W <jgw%sdf.org@localhost> wrote:
> % cd /pkgsrc/foo/pkg-A
> % sudo make clean && sudo make replace
>
> If the above breaks pkg-C:
>
> % cd /pkgsrc/foo/pkg-C
> % sudo make clean && sudo make clean-depends && sudo make update
Orthogonal to this discussion - pkgsrc was modified to use
just-in-time su in the early 2000s, and avoids interesting issues like
fetching sources as root. You are definitely encouraged to use it.
If you'd prefer to use sudo, rather than su, put this in your etc/mk.conf:
.if exists(${LOCALBASE}/bin/sudo)
SU_CMD= ${LOCALBASE}/bin/sudo /bin/sh -c
.endif
Best,
Alistair