Re: add PKG_INSTALL_TRY_UPGRADE -- please review

[matthew sporleder <msporleder%gmail.com@localhost>]

On Thu, Jun 9, 2016 at 9:20 AM, Greg Troxel <gdt%ir.bbn.com@localhost> wrote:
>
> matthew sporleder <msporleder%gmail.com@localhost> writes:
>
>> I'd like to revive this old thread.
>
> What problem are you trying to solve?
>
> I'll assume you are doing updates from sources, rather than using
> someone else's binaries or doing a bulk build yourself.
>
> If you run pkg_rolling-replace, packages are updated ('make replace') in
> order, and it shouldn't happen that a new version of a package is built
> as a dependency when an old version is installed.
>
> If you try to 'make replace' some package, and you haven't run
> pkg_rolling-replace (or 'pkgin fug' with a binary set consistent with
> your source tree), the dependency logic can decide it needs foo>=3 when
> you have foo-2 installed and try to build (which works) and install
> (which fails) a foo-3 package.
>
> Are you trying to have 'make package-install' of foo-3 turn into 'make
> replace' if another foo is installed?
>
> Or something else?


Since it's been three+ years I will restate the problem I was
originally trying to solve:
I am getting pretty sick of the following workflow:

cd /usr/src/pkgsrc; cvs update
cd devel/tig
make install clean

... (an hour later)

pkg_add: A different version of foo-dependency-1.0.1 is already
installed: foo-dependency-1.0.0
pkg_add: 1 package addition failed
*** Error code 1

...
(grumble) pkg_add -u /usr/src/packages/All/foo-depdendency-1.0.1
make install

repeat...

</quote>


I was reading https://wiki.netbsd.org/pkgsrc/how_to_upgrade_packages/
and things don't really seem much better/different than they were
three years ago.