On Sun Apr 29, 2018 at 12:01:21PM +0200, Landry Breuil wrote: > On Sun, Apr 29, 2018 at 11:58:02AM +0200, Rafael Sadowski wrote: > > On Sun Apr 29, 2018 at 11:01:11AM +0200, Landry Breuil wrote: > > > On Sun, Apr 29, 2018 at 10:04:25AM +0200, Rafael Sadowski wrote: > > > > $ cat x11/kde-applications/libkdcraw/pkg/DESCR > > > > Libkdcraw is a C++ interface around LibRaw library used to decode RAW > > > > picture > > > > files. > > > > > > > > Looks simple but it feels like a trap. libkdcraw-17.12.3 has no > > > > conflicts with libkdcraw from KDE4 but we can't just commit because all > > > > KDE4 applications will grep/find libkdcraw-17.12.3 instead > > > > libkdcraw-4.*, which is wrong. > > > > > > Do you mean at install time ? just because the pkgname is the same ? > > > use @option is-branch maybe ? > > > > > > > Exactly, pkgname is the same but somehow everything looks okay: > > > > $ TRUSTED_PKG_PATH=/usr/ports/packages/amd64/all pkg_add gwenview > > gwenview-4.14.3p3:libkdcraw-4.14.3p2: ok > > gwenview-4.14.3p3:libkipi-4.14.3p2: ok > > gwenview-4.14.3p3: ok > > > > The 17.12.3 packages will not fetch. kde4 is smart enough, anyway ok? > > I'm not 100% sure but i think you *have* to at least set @option > no-default-config (maybe is-branch?), otherwise the packages will > conflict by default since they have the same name, even if they don't > have actual files conflicting. >
Yes, both options make sense to me. Btw I didn't know them, so far: @option is-branch @option no-default-conflict Ok (I think a second updated tarball is nor necessary, isn't)?
