> Sent: Tuesday, March 10, 2020 at 4:47 PM
> From: "Ken Moffat via blfs-support" <[email protected]>
> To: "BLFS Support List" <[email protected]>
> Cc: "Ken Moffat" <[email protected]>
> Subject: Re: [blfs-support] Chromium should be in the book
>
> On Mon, Mar 09, 2020 at 09:30:58PM -0500, William Harrington via blfs-support 
> wrote:
> > On 2020-03-08 01:22, Christopher Gregory via blfs-support wrote:
> > >  
> 
> I hadn't thought it necessary to reply to this thread until now, so
> please allwo me to make one comment on the original post before
> replying to William's post.
> 
> > >  
> > >  
> > > 
> > > Sent: Sunday, March 08, 2020 at 7:16 PM
> > > From: "Χάρης Καραχριστιανίδης via blfs-support"
> > > <[email protected]>
> > > To: blfs-support <[email protected]>
> > > Cc: "Χάρης Καραχριστιανίδης" <[email protected]>
> > > Subject: [blfs-support] Chromium should be in the book
> > > After 8.1 Chromium isn't included in the books. It is one of the most
> > > used browsers (I use ungoogled chromium). Maybe it should be added
> > > again? In latest Chromium included at least 1 dependency gives 404, so
> > > even that may not be possible to be installed.
> > > 
> 
> Χάρης, I've only just realised that you might be trying to build
> whichever old version was referenced in the 8.1 book - using such an
> old version in the current "Wild West" internet is a recipe for
> pain.
> 
> [...]
> > > 
> > > Hello,
> > > 
> > > That just goes to show that you did not read the tickets about
> > > chromium.  I spent a considerable amount of time on many different
> > > versions of chromium, and it is a real dog to try to get to work.
> > > Bruce wanted it out of the book, and from a shear maintenance point of
> > > view, ie the time needed to actually find even their so called stable
> > > build that would actually build is a nightmare.  Not to mention the
> > > number of vulnerabilities.  It really is better to be left out of the
> > > book, unless someone is prepared to make sure that all of the
> > > vulnerabilities are patched and that a regular up to date build can be
> > > achieved.  It would require someone to only work on chromium, are you
> > > offering YOUR time to do that?
> > > 
> > > Christopher.
> > 
> > It can be a Hint or have a separate book like CrLFS! Hah!
> 
> With chromium, a hint will become outdated within weeks.  The only
> way to keep up to date with whichever version is currently labelled
> as stable is to look at what distros are doing.
> 
> Maybe https://github.com/Eloston/ungoogled-chromium might be
> slightly less painful, I have no idea.
> 
> I don't agree that chrome/chromium have more vulnerabilities, they
> just have more researchers and they try to put the critical fixes
> out quickly rather than waiting for their next scheduled release
> (firefox - mostly, and qtwebengine always).  But coupled with the
> general churn it becomes impossible.  As people can see from the
> ticket, it is certainly beyond _my_ skills.
> 
> ĸen
> -- 
> #define THE_TRUTH_AND_THATS_CUTTIN_ME_OWN_THROAT true
>             Al Viro, complaining about a 'TRUE' macro in staging
> 
> -- 
> http://lists.linuxfromscratch.org/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
> 

Hello,

The shear time involved with Chromium is not worth it.  You can not even 
guarantee that when a point release comes out, even if you have already spent 
the hours of abortive builds, and managed to get a version to successfully 
build and install and work, that you would get it to build.

From my recollection, the only reason that it was in the book in the first 
place was because mozilla/firefox did not include the widevine plugin that was 
necessary for the drm content to be played, and html5.  That is no longer the 
case.

As Ken pointed out, hints are useless.  The base instructions are in the 
archive version of the book, so if people want to waste their time in 
attempting to get it to work, then that is up to them really.  I certainly did 
not enjoy downloading a "stable" version of the source, and having it abort the 
compilation an hour or so into the build, just to have to repeat it multiple 
times.  Having said that, if people like to waste their time, each to their own.

I also see that Harrington did not offer his own time to create a separate book 
for it, which is what I would expect from him anyway.

Christopher.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
  • [blfs-support... Χάρης Καραχριστιανίδης via blfs-support
    • Re: [blf... Christopher Gregory via blfs-support
      • Re: ... William Harrington via blfs-support
        • ... Ken Moffat via blfs-support
          • ... Christopher Gregory via blfs-support
            • ... DJ Lucas via blfs-support
              • ... Χάρης Καραχριστιανίδης via blfs-support
                • ... Christopher Gregory via blfs-support

Reply via email to