All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-browser] CFT: Chromium 62 in meta-browser
Date: Wed, 15 Nov 2017 11:34:32 -0800	[thread overview]
Message-ID: <CAMKF1soYSpfBApFPmBa1zj1U6nkqJ9+nqPckRser8Y3eWPmRmg@mail.gmail.com> (raw)
In-Reply-To: <20171115174136.GA4530@jama>

>> As for musl: like I said in my original email and on GitHub, the musl
>> build is currently broken. Carrying tons of patches in the recipe is an
>> uphill battle, so unless someone takes the time to work with upstream I
>> don't think it makes much sense to try to keep the build working.
>

musl is relatively newer and support for various components may not be upstream
but it is getting there. There is no alternative than to carry patches
as of now.
and keep forward porting them as the versions advance. We may never get all
of them upstreamed as is the case with many other large packages.

> OK, fair enough, maybe Khem will again chime in and fix it for musl (in
> the meantime we might blacklist it for musl that people don't wait for
> the build to fail).

The patches needs to be redone mostly. Its ok to blacklist it from now.
I wish someone besides me would have cared too.


  parent reply	other threads:[~2017-11-15 19:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 16:28 [meta-browser] CFT: Chromium 62 in meta-browser Raphael Kubo da Costa
2017-11-09 16:54 ` Otavio Salvador
2017-11-09 17:08   ` Raphael Kubo da Costa
2017-11-10 19:49 ` Trevor Woerner
2017-11-11  0:10   ` Ian Coolidge
2017-11-11 17:25     ` Otavio Salvador
2017-11-13 21:51       ` Ian Coolidge
2017-11-13 21:56         ` Ian Coolidge
2017-11-15 12:04 ` Raphael Kubo da Costa
2017-11-15 12:38   ` Martin Jansa
2017-11-15 14:20     ` Martin Jansa
2017-11-15 17:08     ` Raphael Kubo da Costa
2017-11-15 17:41       ` Martin Jansa
2017-11-15 17:49         ` Kubo Da Costa, Raphael
2017-11-15 19:34         ` Khem Raj [this message]
2017-11-23 10:22           ` Ayoub Zaki
2017-11-28  0:52             ` Ian Coolidge
2017-11-28  8:13               ` Ayoub Zaki
2017-11-28 11:58                 ` Otavio Salvador
2017-11-28 12:47                   ` Ayoub Zaki
2017-11-28 13:05                     ` Otavio Salvador
2017-11-28 21:44                       ` Ian Coolidge
2017-12-11 11:30             ` Raphael Kubo da Costa
2017-12-11 11:35               ` Ayoub Zaki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMKF1soYSpfBApFPmBa1zj1U6nkqJ9+nqPckRser8Y3eWPmRmg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.