#14910 closed bug (fixed)
Add libdvdnav, libdvdread, libdvdcss and libbluray to buildsystem deps
Reported by: | Barrett | Owned by: | kallisti5 |
---|---|---|---|
Priority: | high | Milestone: | R1/beta2 |
Component: | Build System | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
- We need to get libdvdnav and libdvdread into the buildpackages for ffmpeg
- It needs to be done for all architectures
Change History (5)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
I added libdvdread, libdvdnav, libbluray to x86_64 in hrev53887. We don't have native gcc2 packages for these on 32-bit. Assuming BuildFeature is used properly, it shouldn't be a big deal (the add-on you're developing just won't be included if the build-packages isn't available.)
comment:3 by , 6 years ago
Hi pulkomandy, I follow Fedora mainly for legality in software because they have the Red Hat legal team on their side. They have a page on DVD playback (https://fedoraproject.org/wiki/Multimedia/DVD), and VideoLAN has a page on legal (https://www.videolan.org/legal.html). From what I understand, libdvdcss does not have encryption keys included, but has a method to extract the keys using the algorithm of CSS. It is a similar issue with libaacs, which only implements the AACS specification and does not include keys. I may be incorrect about libdvdcss, but from what I understand, as long as we are not also publishing software that actively allows for ripping of DVDs to raw format without copy protection, we should be fine, YMMV and all.
comment:5 by , 5 years ago
Milestone: | R1 → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
IIRC, libdvdcss contains encryption keys that we definitely cannot include in Haiku for legal reasons. Are the others of any use without that?