Bug 47130 – motiontrack-0.1.0 (new ebuild)

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Corvus 2004-04-07 11:45:17 UTC]

a new ebuild, a maintainer should look over it for mistakes.

motiontrack can either use libgd or imagemagick for image io
libgd might be faster but imagemagick supports more image formats
and has better debugging support

I hope the taken approach is apropriate,
i have asked in the gentoo-dev ml after all :-)


Reproducible: Always
Steps to Reproduce:

[Comment 1 Corvus 2004-04-07 11:48:00 UTC]

Created attachment 28840 [details]
the ebuild

[Comment 2 Sami Näätänen 2004-04-07 12:37:24 UTC]

DEPEND="libgd? ( media-libs/libgd )
 	imagemagick? ( media-gfx/imagemagick ) : ( media-libs/libgd )"

If I haven't made any mistakes then the next DEPEND will take care of the debug case (use flag), which the above DEPEND (used in the ebuild) does NOT do.

DEPEND="libgd? ( media-libs/libgd )
 	imagemagick? ( media-gfx/imagemagick )
	!libgd? (
	    !imagemagick? (
		debug? ( media-gfx/imagemagick ) : ( media-libs/libgd )
	    )
	)"

[Comment 3 Sami Näätänen 2004-04-07 14:51:27 UTC]

Final corrected version. (From the users mailinglist thread)

DEPEND="debug? ( media-gfx/imagemagick )
 	!debug? (
 		libgd? ( media-libs/libgd )
 		!libgd? (
			imagemagick? ( media-gfx/imagemagick )
			!imagemagick? ( media-libs/libgd )
		)
 	)"

[Comment 4 Corvus 2004-04-10 02:14:14 UTC]

Created attachment 29012 [details]
new version of the ebuild

i tried the 

DEPEND="
useflag? (...)
!useflag? (...)
"
approach, but it somehow created a block (B) on imagemagick when none of the
useflags were set, so I used the ":" 'else' syntax instead, which seems to
work.

[Comment 5 Corvus 2004-07-18 22:55:13 UTC]

update:

recent bug reports from motiontrack users showed, that the program cant be build with all features (especially speed enhancements) enabled with imagemagick versions prior to  5.5.7, since they dont have the ExportImagePixels() function

so while the current cvs version of motiontrack already trys to cope with that in the ./configure script and disable that feature with old imagemagick versions, this is not yet the case with motiontrack-0.1.0 so that has to be handled in the ebuild

the ebuild should then probably DEPEND on =media-gfx/imagemagick-5.5.7* instead of just any media/gfx/imagemagick, i hope that syntax is correct

[Comment 6 Chris White (RETIRED) 2004-07-19 23:28:45 UTC]

Now in portage, added the imagemagick magic (pun intended) to the ebuild as well.  `emerge sync` for it :).