Bug 310 - ffmpeg spec file is still configured to for use with PLF repository
Summary: ffmpeg spec file is still configured to for use with PLF repository
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 18:33 CET by Barry Jackson
Modified: 2011-06-06 20:03 CEST (History)
1 user (show)

See Also:
Source RPM: ffmpeg-0.6.1-2.mga1.src.rpm
CVE:
Status comment:


Attachments

Description Barry Jackson 2011-03-08 18:33:39 CET
Description of problem: I understand that there will be no PLF repo in Mageia, but ffmpeg spec file is set to only add non-free features when building for PLF.
If the intention is to have non-free codecs enabled in the tainted repo, then can I suggest that libfaac is also enabled in ffmpeg by default if this is possible under whatever license is involved - (of which I know nothing).
I guess this would involve also making libfaac a dependency of ffmpeg.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Dimitrios Glentadakis 2011-03-08 18:42:19 CET

CC: (none) => dglent

Comment 1 Ahmad Samir 2011-03-08 19:16:19 CET
Once it's decided how packages will be pushed to the tainted repo, this will be fixed.
Comment 2 Manuel Hiebel 2011-06-06 14:01:41 CEST
ffmpeg is now in tainted

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 3 Ahmad Samir 2011-06-06 20:03:44 CEST
Actually, they way the spec is done is we just reuse the plf macros in there, no need to reimplement them (sometimes the plf macros are too many, lots of enabled/disabled codecs); so pterjan just used:
%if "%distro_section" == "tainted"
%global build_plf 1
%endif

easier this way and also makes syncing the specs between mdv and mga faster.

Note You need to log in before you can comment on or make changes to this bug.