From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mail.openembedded.org (Postfix) with ESMTP id 29AE565C8A for ; Wed, 7 Dec 2016 16:02:20 +0000 (UTC) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP; 07 Dec 2016 08:02:21 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,310,1477983600"; d="scan'208";a="14954818" Received: from kanavin-desktop.fi.intel.com (HELO [10.237.68.161]) ([10.237.68.161]) by orsmga002.jf.intel.com with ESMTP; 07 Dec 2016 08:02:17 -0800 To: Andreas Oberritter , openembedded-core@lists.openembedded.org References: <1481024991-5882-1-git-send-email-obi@opendreambox.org> <5106886a-56c8-79f3-bd7a-aee780fd590b@linux.intel.com> From: Alexander Kanavin Message-ID: Date: Wed, 7 Dec 2016 18:02:32 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0 MIME-Version: 1.0 In-Reply-To: Subject: Re: [PATCH 00/33] Accumulated patches for deb packaging X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2016 16:02:21 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 12/07/2016 05:30 PM, Andreas Oberritter wrote: >>> These are most of my patches which accumulated since our distro >>> switched from opkg to dpkg and apt two years ago. They were tested >>> thoroughly on dora and krogoth and just a little bit on master. >> >> How about updating apt and dpkg to latest upstream releases at the same >> time? > > I don't see an advantage over updating at a later point in time. The advantage is that oe-core does not accumulate technical debt that way. Specifically, it's better to do many incremental version updates than few massive updates (or avoid updates altogether until the ongoing maintenance becomes unbearable, in the worst case). There is less changes in upstream code to deal with, less dependency fixing, and less resistance from community. This is actually the preferred mode of operation in oe-core. We are constantly fighting back against the increase in debt, and you could really help us here a bit. Regards, Alex