Re: gnupg2: fail with libgpg-error 1.47

[tlaronde%kergis.com@localhost]

On Thu, Jan 09, 2025 at 02:56:36PM +0100, Thomas Klausner wrote:
> On Thu, Jan 09, 2025 at 02:54:47PM +0100, tlaronde%kergis.com@localhost wrote:
> > OK, so let's look at the reverse: a dependency is happy with X and
> > build, then package depending on it requires Y, and when you replace X
> > by Y, you pull the carpet under dependency. How does it work in this
> > case?
> 
> That depends on the way you maintain your system.
> 
> The way I do it, I build binary packages in a pbulk, so I have the
> latest version of every package available, and then I update with
> pkgin. There's no problem in that case.

I guess it is the only way to be safe... But how I would love if
(upstream) developers would link statically against trivial libraries
and/or version correctly dshared libraries so that concurrent versions
could be installed without imposing a "total" dance.

But pkgsrc is not responsible for that.

Thanks,
-- 
        Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C