From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f174.google.com (mail-yw0-f174.google.com [209.85.161.174]) by mail.openembedded.org (Postfix) with ESMTP id 6A6B078367 for ; Tue, 15 Aug 2017 14:43:07 +0000 (UTC) Received: by mail-yw0-f174.google.com with SMTP id u207so5914686ywc.3 for ; Tue, 15 Aug 2017 07:43:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WS/qQ6OR9VBwhoYdOkD7QvNLrX6d+oyDIMO8oUapAjY=; b=U2gIWDXpVnSqQJ/qygHkapdlmuNusvjMK6Ug5w+dAE8m7NW1yKd5TjMo8VZa7ohWRd YJKRWBig491RXdf+sodUcQkwTmfcNxo7yZq1AKgQ9yMwYyPUiRrlm5OxIze4U1jVuzGf RHee7BjPFLT7J1saUEBEoB8NDZn5jhZ6iYfeC5wfY8iIxi5S+2EgwT6kIK0M9VOqhp4N qPAF5XWuVz6GBwHdV8VW9fZyEBp9qCjg13vPrhGJz8x3uMlEEYO3+bgeZEX7s8xOgGjW hvokcKimSPzouwfjNU8iKLNRvMQ/0Z0ZxloKUtaDXz92Sgt06mtoNSxUslhWR3Xkxl9s Cgzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WS/qQ6OR9VBwhoYdOkD7QvNLrX6d+oyDIMO8oUapAjY=; b=kjt5wWo+vc5gHjjx+gazbDin9jyz4qHHSgxLJdOLLqGF9SxnuucKp2TLfeTbuzhJ+d OYyzu4AS/DssERquyu5cPwrdO+eBdNd3vqCNBYO82qDt8qmDNGX6fKxCs76W1pnnRVeH zDQ/ivXcfYa2KlCiNC//JkOk0gqT5WIDzPm01BdZVjYS0NL0Enz244vzdb4P+p5kYD/p 65RWObefrrfYglsDZTzcYWfPtBiSaJVkCRNCG3IJACIZmaqW4r6IIoDzrHdYlZWPSHrA ejAYt1UmzzDt0sdfnrQbH/XoGfbcwIjwjDIqqOkaYatpZXx44CJyk5HZJXJikoeSf8at onwQ== X-Gm-Message-State: AHYfb5iYNCRgwgr5Q0GluLMzNNPgKeNZhUVpIiK9CfWaJmWbA6LLttZ4 gF1A+khapYTxHXgKUZVxrPPMjgHfzg== X-Received: by 10.37.175.19 with SMTP id a19mr8275665ybh.291.1502808188193; Tue, 15 Aug 2017 07:43:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.66.151 with HTTP; Tue, 15 Aug 2017 07:43:07 -0700 (PDT) In-Reply-To: <87wp65rnfk.fsf@rkubodac-desk.ger.corp.intel.com> References: <87wp65rnfk.fsf@rkubodac-desk.ger.corp.intel.com> From: Trevor Woerner Date: Tue, 15 Aug 2017 10:43:07 -0400 Message-ID: To: Raphael Kubo da Costa Cc: "openembedded-devel@lists.openembedded.org" Subject: Re: chromium detected as stripped X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Aug 2017 14:43:07 -0000 Content-Type: text/plain; charset="UTF-8" On Tue, Aug 15, 2017 at 9:05 AM, Raphael Kubo da Costa wrote: > The main reason why I opted to start my recipe from scratch at the time > was simplicity: the meta-browser repository used the same recipe for > Chromium, CEF and Chromium with Ozone-Wayland, offered many different > options and shipped quite a few patches that made updates quite > difficult. I agree 100% (or more). This is why, earlier this year, I removed CEF (which wasn't working, hadn't been working in over a year, and (apparently) nobody was using). This is also why I also split out "pure" chromium and chromium-wayland recipes. Trying to do everything in one recipe was getting too onerous. In my own (failed and therefore put on the back-burner) efforts to update the chromium (x11) recipe to 59 and 60 I too created a recipe from scratch without all the baggage of debug vs non-debug, no packageconfigs, multiple architectures, component build, and without pulling in any *.inc files. Just a small, self-contained recipe. > My recipe is a lot less customizable, but OTOH that makes it > quite easy to move to new Chromium milestones. If we're able to find a > balance there, I definitely think we'd be able to get a lot more done > together. I think it was a mistake for meta-browser to have recently added a huge number of patches supporting musl. One commit alone added almost 700 lines of diff for musl support (not to mention the subsequent fixup patches)! Musl support should be kept and maintained in meta-musl, isn't that the purpose of meta-musl? If users want musl support they're going to need to add meta-musl anyway, so it's no change from a user's point of view. But 700 lines of patches provides a heavy burden for anyone trying to maintain or update meta-browser's chromium, especially if they don't use or care about musl support.