Re: packages w/introspection option out-of-order update

[maya%netbsd.org@localhost]

On Mon, Jun 25, 2018 at 04:58:31PM -0400, Greg Troxel wrote:
> 
> "John D. Baker" <jdbaker%mylinuxisp.com@localhost> writes:
> 
> > On Mon, 25 Jun 2018, Greg Troxel wrote:
> >
> >> "John D. Baker" <jdbaker%mylinuxisp.com@localhost> writes:
> >> > So far, I ran into:
> >> >
> >> >   clutter-gtk <- clutter <- {cogl,json-glib}
> >> >   gst-plugins1-base <- gstreamer1
> >
> > Maybe not a pkg_rr thing at all.  Probably stale packages built during
> > the time when "introspection" was being thwarted by (as yet not understood)
> > toolchain problems.
> >
> > "graphics/cogl", "textproc/json-glib", "graphics/clutter", and
> > "multimedia/gstreamer1" were all missing their various "Foo-X.Y.gir"
> > files which were needed when building "graphics/clutter-gtk" and
> > "multimedia/gst-plugins1-base".
> >
> > They all gained default-enabled "introspection" options long ago (4+
> > years!) but the package has remained the same.  Thus they were considered
> > up-to-date, but "clutter-gtk" and "gst-plugins1-base" needed updating.
> >
> > With "introspection" no-longer disabled locally, they must have run into
> > dependencies built back when "introspection" _was_ disabled locally but
> > did not change version/pkgrevision in the meantime.
> >
> > That seems more likely the case.  If you built with "introspection"
> > disabled at some point and now build with it enabled, watch out for
> > such stale dependencies.
> 
> That's a good point.  Basically, changing options in mk.conf is
> equivalent to editing the default list in options.mk, which requires
> revbumping.  But pkgsrc currently doesn't notice.
> 
> It would be nice to have a way to iterate over all installed packages
> and for each, get the options that would be used, and the options that
> were used, and if different mark the package unsafe_options, and then
> union those packages into pkg_rr's list (with unsafe_depends and
> rebuild).  Patch welcome :-)
> 

We have all the information to know a package got changed by the RCSIDs
of the package components (also stored in the package binary) but we
probably don't want to rely on CVS.