Re: CVS commit: pkgsrc/editors/zim

["OBATA Akio" <obache%netbsd.org@localhost>]

On Sun, 17 Feb 2013 08:53:08 +0900, Christoph Badura <bad%netbsd.org@localhost> 
wrote:

> On Sat, Feb 16, 2013 at 10:39:15AM +0900, OBATA Akio wrote:
> > >Don't depend on py-gobject and py-gtk2 directly, use the py-gtk2 buildlink3.mk.
> > Please revert the part.
> >
> > buildlink3.mk should not be used if it is not required.
> > `required` means the package using header files or pkgconfig files from it.
> > buildlink add direct dependency, and adding certain ABI dependency on it too.
> > It seems that `zim' is pure python application, it should not be done
> > (or if gtk2 or depending packages's ABI is changed, zim also will be rebuilt).
>
> Yes, I believe that is what we want.  If py-gtk2 requires a different
> API/ABI from gtk2 it will also expose a different API/ABI to the
> packages that require it.  And those packages need to be rebuilt in
> order to adapt to the different API/ABI.  That *is* why py-gtk2 provides
> a buildlink3.mk file.  Otherwise the py-gtk2/buildlink3.mk should be
> deleted.

Yes and No.

> Unfortunately the buildlink documentation in pkgsrc.txt is obviously
> out-of-date regarding buildlink3.mk usage in cases like this.  Maybe you
> want to take it to tech-pkg to clear up that point.

My broken English will provide misleading information,
so please someone else...

> Personally I think it is a waste of time.  If a package provides a
> buildlink3.mk file it should be used by other packages that depend on it.

But unwanted usage of buildlink.mk file raise unwanted rebuilding packages
for all pkgsrc users.
Now, update of png to 1.6 introduce big recursive revision bump.
Some of them might unnecessary revision bump, like editors/zim.
My machine is not so fast, so I want to reduce such unwanted rebuild.

--
OBATA Akio / obache%NetBSD.org@localhost