On Mon, Apr 18, 2016 at 3:24 PM, Johnny Hughes <johnny at centos.org> wrote: > On 04/18/2016 09:06 AM, Phelps, Matthew wrote: > > On Mon, Apr 18, 2016 at 9:56 AM, Karanbir Singh <kbsingh at centos.org> > wrote: > > > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> On 18/04/16 14:15, Phelps, Matthew wrote: > >>> Thanks. I imagine (hope?) there shouldn't be too much effort to get > >>> this to work, since it's already been done upstream. RedHat > >>> continues to push out updates even. E.g. > >>> https://rhn.redhat.com/errata/RHSA-2016-0638.html > >>> > >> > >> that looks like Supplementary content - we've never had that before. > >> > >> what we might need to do here is work the upstream beyond Red Hat > >> where this works done, that makes it Supplementary content and not > >> completely open source. Do we atleast know at this point what that > >> might be ? > >> > >> regards > >> > >> - -- > >> Karanbir Singh, Project Lead, The CentOS Project > > > > > > I suspect it has to do with their "pepperflash" flash plugin. > > > > Clearly flash is on the way out, so any support for it is not necessary. > > > > It is indeed not completely open source. I was told that the agreement > between Red Hat and Google only allows the RPMs for RHEL to be released > to subscribers on the supplemental channel. > > Sorry, but I can't release it. > > > That was my understanding, that we have a "political" (really legal) issue, not a technical issue. I hope Karanbir can re-visit this with RedHat. Does anyone have a cookbook for building chromium under CentOS 6? Johnny, do you think you could release the steps you took to build what you did? -- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphelps at cfa.harvard.edu, http://www.cfa.harvard.edu