graphics/p5-Image-ExifTool and graphics/py-exif both install bin/exiftool. Fix: Add CONFLICTS to the ports Makefiles. How-To-Repeat: Install both ports.
State Changed From-To: open->feedback Awaiting maintainers feedback
Sure enough, these two ports conflict. However, there is currently another outstanding PR for graphics/p5-Image-ExifTool which also modifies the Makefile; I'll wait until ports/92150 is resolved before submitting a patch to close this PR. Thanks, -- Tod McQuillin
Responsible Changed From-To: freebsd-ports-bugs->lawrance Take it; I'm looking at the p5-Image-ExifTool update now.
State Changed From-To: feedback->feedback p5-Image-ExifTool update completed. Got a patch?
How about working around the conflict: http://bsd.gubkin.ru/myports/py-exif.diff If this diff makes it through, a committer might also place an exiftool->py-exiftool rename note in ports/UPDATING
State Changed From-To: feedback->closed CONFLICTS added. Thanks!
I'm sorry, but did you notice my bug follow-up? I posted this patch: http://bsd.gubkin.ru/myports/py-exif.diff Somehow making it impossible to use important bindings for two popular languages on the same FreeBSD system does not seem right, does it? Thanks!
On 17/03/2006, at 4:32 PM, Andrew Pantyukhin wrote: > I'm sorry, but did you notice my bug follow-up? I posted > this patch: http://bsd.gubkin.ru/myports/py-exif.diff > > Somehow making it impossible to use important bindings > for two popular languages on the same FreeBSD system > does not seem right, does it? Well, OK. But why is the diff so big? Shouldn't it just be a one- line change for ${INSTALL_SCRIPT} line for exiftool?
State Changed From-To: closed->open I missed a patch.. let's analyse.
On 3/17/06, Sam Lawrance <lawrance@freebsd.org> wrote: > > On 17/03/2006, at 4:32 PM, Andrew Pantyukhin wrote: > > > I'm sorry, but did you notice my bug follow-up? I posted > > this patch: http://bsd.gubkin.ru/myports/py-exif.diff > > > > Somehow making it impossible to use important bindings > > for two popular languages on the same FreeBSD system > > does not seem right, does it? > > Well, OK. But why is the diff so big? Shouldn't it just be a one- > line change for ${INSTALL_SCRIPT} line for exiftool? > > Clean-up's :-) Portlint is happy now
On 17/03/2006, at 5:45 PM, Andrew Pantyukhin wrote: > On 3/17/06, Sam Lawrance <lawrance@freebsd.org> wrote: >> >> On 17/03/2006, at 4:32 PM, Andrew Pantyukhin wrote: >> >>> I'm sorry, but did you notice my bug follow-up? I posted >>> this patch: http://bsd.gubkin.ru/myports/py-exif.diff >>> >>> Somehow making it impossible to use important bindings >>> for two popular languages on the same FreeBSD system >>> does not seem right, does it? >> >> Well, OK. But why is the diff so big? Shouldn't it just be a one- >> line change for ${INSTALL_SCRIPT} line for exiftool? >> >> > > Clean-up's :-) Portlint is happy now I don't think it's worth removing the pkg-plist if you have to add so much extra stuff in to the makefile. I'll keep it simple and just use %%DOCSDIR%% as portlint suggests.
On 3/17/06, Sam Lawrance <lawrance@freebsd.org> wrote: > > On 17/03/2006, at 5:45 PM, Andrew Pantyukhin wrote: > > > On 3/17/06, Sam Lawrance <lawrance@freebsd.org> wrote: > >> > >> On 17/03/2006, at 4:32 PM, Andrew Pantyukhin wrote: > >> > >>> I'm sorry, but did you notice my bug follow-up? I posted > >>> this patch: http://bsd.gubkin.ru/myports/py-exif.diff > >>> > >>> Somehow making it impossible to use important bindings > >>> for two popular languages on the same FreeBSD system > >>> does not seem right, does it? > >> > >> Well, OK. But why is the diff so big? Shouldn't it just be a one- > >> line change for ${INSTALL_SCRIPT} line for exiftool? > >> > >> > > > > Clean-up's :-) Portlint is happy now > > I don't think it's worth removing the pkg-plist if you have to add so > much extra stuff in to the makefile. I'll keep it simple and just > use %%DOCSDIR%% as portlint suggests. > > > Listen to your heart :-)
State Changed From-To: open->closed Committed, thanks!