From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6478179128234213376 X-Received: by 10.223.186.140 with SMTP id p12mr209584wrg.16.1508328558336; Wed, 18 Oct 2017 05:09:18 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.47.194 with SMTP id v185ls820169wmv.9.canary-gmail; Wed, 18 Oct 2017 05:09:18 -0700 (PDT) X-Google-Smtp-Source: AOwi7QBkBfj08U1WcACj1MuRSmjsIRA1fyvhQGyfH/fVJGJN7LF7WxqO+Rtnr+xp/uaysKktmiCW X-Received: by 10.223.185.26 with SMTP id k26mr1501645wrf.22.1508328558105; Wed, 18 Oct 2017 05:09:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508328558; cv=none; d=google.com; s=arc-20160816; b=q5sNDMmWq91LmMnNqsKNjlRKIxz3Ve9rIso+i+uKemXQaeYnCDMe9G3tCG70SW7jzn OkFp7ushJd67LSmTXTU5jXsqvccyPs2CUpC3JYJqInUytMua1GNcytrunoK3gLJ73WM2 6jco5yTAEtapfV3W5/hgvjVGRUFLqAkEEXJxB7HrHkbaSRsF4fSq3q1lhQ69LbFIFtTw PBx06dGmaT50i5VTG68uSF6V9ev/sQ8/6D2UGDZ0Df/MGG+6cg8jQo3SR0wNpvipVjds dhCKuD920FeO2he1tRyat649yrsEkAqcqTEE/gOQ2nIOu0bceIXwMRkrEj0ufJWOoHtG 7Ejw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=V3ohvCZnEmssTgz8vUk0XNWoVdpj4lhkBQpC/ykaqDQ=; b=Gi3DWMgrN+M61tdRywl432qSp/PLXO1aWqh8OyioxgwuwUJ/RHadWvJPC3+G8vfRA5 oLThAqaVY7HxVXE182kWT9n8HdLaxDVi2CAdpR/u/ruTkTvYbf+KeCtxp74HiAhEPV83 8vXyi3C1AjlbEQmaaC0/XVIA61ERKHXcE/I9NmQr5lQX3B/QUgfYrrLzV+mfZFFVzOmQ TEqZjWc3EC7l4AhukvnRH0FnnKSlJA7/bI7KZBkUQodPktvHTb6f2LA2X0aUyHAOtCG5 OyA+BSt9IGOzDRGq1mOBaBRqh3Bd8DNOme9aZ3z+fbiyk+mowlwIV1hLSWEP+wCzmaDC MEIQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id r65si443799wmf.2.2017.10.18.05.09.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Oct 2017 05:09:18 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id v9IC9HdK030345 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 18 Oct 2017 14:09:17 +0200 Received: from md1f2u6c.ww002.siemens.net ([158.92.8.8]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id v9IC9GMf031507; Wed, 18 Oct 2017 14:09:17 +0200 Subject: Re: Isar fork To: Ben Brenson , isar-users References: <8fe13268-9bfa-4b24-897a-133c9530c188@googlegroups.com> From: Jan Kiszka Message-ID: Date: Wed, 18 Oct 2017 14:09:16 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: XhtASICdwTi/ On 2017-10-18 13:56, 'Ben Brenson' via isar-users wrote: > Hi Jan, > yes you are right, the baseline of the isar fork is quiet old. > We had to implement some features quiet fast to get a first image build > working. > Combined with the open source agreement, we forked this repository  and > started developing. > > Since a lot of the codebase has changed, related to 25 May, a little bit > of effort is required to work out some patches, but I will try do handle > this. > The first feature I intent to post, would be the chroot related stuff, > because the most changes are related to the bitbake core itself, which > should be at the same state as > my repository. > > So adding this feature won't force Isar to make use of them, but the > possibility of using them may be available after. > So I think I will start with that feature, by submitting patch series. Yes, start with the simplest, best isolated feature first. That will help get the ball rolling. > > The other features will dive very deep into isar, and the codebase > differs a lot now. > This fact never offered the possibility of frequently rebasing against > upstream. > So rebasing now against the main repository will be a time consuming > job, but is required :-( I fully understand, and something similar happened to us before. If project pressure comes in, you can easily be forced off-track and then have to pay the price later on. However, it would have been valuable to participate in the requirement discussions early. That might have enabled us to prioritize features and sharpening their scope to address your needs as well. > > May be rebasing the current Isar features against my repo will be much > easier to handle, > but doesn't that miss the goal of getting my features mainlined into > current mainline Isar? Indeed. Upstream is Isar, not a specific fork of it. By now, we are working on a number of products that build upon upstream Isar, are mostly happy, but will surely further improve the core to improve the usability. Eventually, you will miss those features in your fork, I'm sure. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux