Ungoogled chromium drm2/19/2023 Ungoogled-Chromium is no different: running > the user when they want to, for example, do guix build -S chromium.Īs Leo says, `guix build -source` should never return nonfree softwareĪs a matter of policy. If not it still amounts to distributing non-free software to > compile should itself be 100% free software and FSDG compliant from the ![]() > clean-up program after downloading the source, even if that has been > should not be hidden/removed after the fact by asking the user to run a > just like build flags, should not be sufficient. > other packages have their freedom problems fixed in this way but this, > ungoogled-chromium over it, and then building. > building seems to involve downloading Chromium, then runnning > Taking this and considering Guix's build process: The method of > * Google Toolbar is in there, with a non-free EULA Did you record the absolute paths to these files? I cannot find these images: grepping for CC-BY-NC-SA or 'CreativeĬommons' did not aid. > * third_party/blink has some images under CC-BY-NC-SA-2.0 I don't mean that to be an exhaustive list of everything, > Even in the short time I was reviewing it I found a number of freedom The tarball produced by `guix build -source ungoogled-chromium`. To avoid duplicate work, it would be useful if you ran this analysis on > indicate that which is very clearly free software and that which needs > fully vetted any particular results but it does help to at least > Of course, automated licenses analysis is never perfect and I have not ![]() Actually, less than a third of the total files > recently submitted upstream's Chromium. I can open another bug over this if needed. > understand this is not exactly related to the DRM matter but it does > A different but related matter is the build process itself. Bug#34565: ungoogled-chromium contains Widevine DRM
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |