Bug 614592

Summary:	mjpegtools requires users to install additional packages: why not handle with USE flags?
Product:	Gentoo Linux	Reporter:	Donald <dcljr>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED INVALID
Severity:	enhancement	CC:	mgorny
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Donald 2017-04-04 02:59:08 UTC

mjpegtools-2.1.0-r2 provides the following post-install message:

* mjpegtools installs user contributed scripts which require additional
* dependencies not pulled in by the installation.
* These have to be installed manually.
* Currently known extra dpendencies are: ffmpeg, mencoder from mplayer,
* parts of transcode, mpeg2dec from libmpeg2, sox, toolame, vcdimager, python.

I don't understand why the ebuild isn't set up to properly handle these dependencies. At minimum, there should be a local USE flag to force building of all of these dependencies. Better yet, more granular USE flags should be provided to pull in only what is needed by specific scripts.


Reproducible: Always

Steps to Reproduce:
1. emerge media-video/mjpegtools
2. observe post-install message

Actual Results:  
User is told there are other things they may need to install separately.

Expected Results:  
mjpegtools should either depend on these other packages or (since there are many of them) provide local USE flags that could be examined by users before build time to specify which dependencies they do or don't want to install.

Comment 1 Donald 2017-04-04 03:02:33 UTC

Of course, I meant: At minimum, there should be a local USE flag to force building of all of these dependencies that aren't already installed.

Comment 2 Michał Górny archtester

2017-04-08 07:41:17 UTC

USE flags would require users to unnecessarily rebuild this large package for every dep change.

Comment 3 Donald 2017-04-09 03:37:09 UTC

I don't see why that would be a problem, assuming the USE flags were implemented correctly. But FYI, I had to rebuild this package recently (which prompted this bug report in the first place), and it took a whopping 1 minute 8 seconds. There are many much, much larger packages that have lots of USE flags for users to choose from. Not sure why this package has to be different....