From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 9ADACE00E0F; Wed, 24 Jul 2019 13:08:38 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at https://www.dnswl.org/, * medium trust * [198.47.23.248 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid Received: from lelv0143.ext.ti.com (lelv0143.ext.ti.com [198.47.23.248]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 57BD8E00E07 for ; Wed, 24 Jul 2019 13:08:36 -0700 (PDT) Received: from lelv0265.itg.ti.com ([10.180.67.224]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id x6OK8Z4l067373 for ; Wed, 24 Jul 2019 15:08:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1563998915; bh=LJT/Iu0oolA/oNxn9Vk7NYhu0a4gRWRSZAdFl2cXfkA=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=ecn9m1d95wC8waCd2VLGz18PedZR04OLCObusXH8zJkO0VbxOJRqCVzgo46HOVy89 XelcMtADfOmBbwNEzv7zEanCf3vj51R2C2SlG6WHcsFxMv59bV/D2UWECCs6nNm3If plaN+B7ZFgA7cNxeahk0HFjEgQbH8/QKyixGG1hQ= Received: from DFLE112.ent.ti.com (dfle112.ent.ti.com [10.64.6.33]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x6OK8ZDN003762 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Wed, 24 Jul 2019 15:08:35 -0500 Received: from DFLE112.ent.ti.com (10.64.6.33) by DFLE112.ent.ti.com (10.64.6.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 24 Jul 2019 15:08:35 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DFLE112.ent.ti.com (10.64.6.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Wed, 24 Jul 2019 15:08:35 -0500 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id x6OK8Z46060890; Wed, 24 Jul 2019 15:08:35 -0500 Date: Wed, 24 Jul 2019 16:08:35 -0400 From: Denys Dmytriyenko To: "Andrew F. Davis" Message-ID: <20190724200834.GH5700@beryl> References: <20190719210619.18583-1-afd@ti.com> <20190719210619.18583-3-afd@ti.com> <20190724191412.GE5700@beryl> <0c9d5d9a-064c-2481-eff1-90fe69195549@ti.com> MIME-Version: 1.0 In-Reply-To: <0c9d5d9a-064c-2481-eff1-90fe69195549@ti.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Cc: meta-ti@yoctoproject.org Subject: Re: [thud/master][RFC PATCH 3/3] ti-sgx-ddk-um: Drop omap5-sgx-ddk-um-linux package X-BeenThere: meta-ti@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-ti layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jul 2019 20:08:38 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Wed, Jul 24, 2019 at 03:30:57PM -0400, Andrew F. Davis wrote: > On 7/24/19 3:14 PM, Denys Dmytriyenko wrote: > > On Fri, Jul 19, 2019 at 05:06:19PM -0400, Andrew F. Davis wrote: > >> No one depends on this and it does not really get built, > >> remove this from PROVIDES. > > > > Bah, such a nice commit message. :) > > > > Seriously though, it is there for backward compatibility. That was the name > > of this package few years ago. Sure, "it does not get built", but claiming > > that "no one depends on this" is really a guess. There might be old recipes > > out there depending on this package by its old name... > > > > Anyway, I don't mind dropping this backward compatibility, since it's been > > several years already, but I would like to see a better commit message. > > How does backwards compat work with Yocto? Are you saying for out of > tree recipes? If so I'll change the wording to "No one *in-tree* depends > on this". Yes, out-of-tree. Yocto Project embraces layered structure. There are tons of layers with interdependencies. There could be outdated layers (potentially customers) that use the old name. In order to drop backward compatibility, we need to provide a clear message. -- Denys