ilto:g...@lexort.com) >
Dátum: 2017 szeptember 30 18:09:06
Tárgy: Re: package upgrade strategy
Címzett: r0ller < r0l...@freemail.hu (Link -> mailto:r0l...@freemail.hu) >
pkgsrc is designed, more or less, to have packages built consistently
from the same source tree. You can often ge
pkgsrc is designed, more or less, to have packages built consistently
from the same source tree. You can often get away with having some
packages be old. Other than the old packages not depending on or being
dependencies of newer ones, you're on thin ice.
If a package is not available in a
Date:Thu, 28 Sep 2017 22:20:50 +0200 (CEST)
From:r0ller
Message-ID:
| but I hoped that there's a way to avoid compiling relatively big programs
| (like seamonkey) in a case when I just want
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 < a...@pkgsrc.org (Link -> mailto:a...@pkgsrc.org) >
Dátum: 2017 szeptember 28 18:20:31
Tárgy: Re
I suspect this is more fallout from people mis-updating libraries.
try manually deleting and adding midori again. I'm hoping it rebuilt the
package even though there's no indication to the binary package bits
that it changed.
r0ller writes:
> Hi Brad,
>
> I'd do that if it was possible (having the newest versions of all my
> packages) but as said, midori is not available any more in the 7.1 package
> repo so it cannot be upgraded (not even the same version of midori is
> available with just an
On Thu, 28 Sep 2017, r0ller wrote:
> By the way, what kind of difference is indicated by the number in the
> 'nb' suffix?
Means the original code (upstream source) was not changed. The nb means
we may be building or installing it differently (like due to a new
patch, new build option, or a
Alistair Crooks wrote:
> On 28 September 2017 at 08:40, Jeff_W 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
On 28 September 2017 at 08:40, Jeff_W 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
> I hope someone can give an answer to this question from a newbie: how can
> I handle situations when an already installed package (say A) needs to be
> upgraded due to a newly installed package (say B) as it's being a
> dependency for it but another already installed package (say C) still
>
Feladó: Brad Spencer < b...@anduin.eldar.org (Link ->
mailto:b...@anduin.eldar.org) >
Dátum: 2017 szeptember 28 14:13:53
Tárgy: Re: package upgrade strategy
Címzett: r0ller < r0l...@freemail.hu (Link -> mailto:r0l...@freemail.hu) >
r0ller <r0l...@freemail.hu> writ
11 matches
Mail list logo