All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Andrew F. Davis" <afd@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [thud/master][RFC PATCH 3/3] ti-sgx-ddk-um: Drop omap5-sgx-ddk-um-linux package
Date: Wed, 24 Jul 2019 16:08:35 -0400	[thread overview]
Message-ID: <20190724200834.GH5700@beryl> (raw)
In-Reply-To: <0c9d5d9a-064c-2481-eff1-90fe69195549@ti.com>

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


  reply	other threads:[~2019-07-24 20:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 21:06 [thud/master][RFC PATCH 1/3] ti-sgx-ddk-um: libgbm is now part of this project Andrew F. Davis
2019-07-19 21:06 ` [thud/master][RFC PATCH 2/3] ti-sgx-ddk-um: Add expat as runtime dependency Andrew F. Davis
2019-07-24 19:24   ` Denys Dmytriyenko
2019-07-24 19:29     ` Andrew F. Davis
2019-07-24 20:27       ` Denys Dmytriyenko
2019-07-24 21:31         ` Andrew F. Davis
2019-07-19 21:06 ` [thud/master][RFC PATCH 3/3] ti-sgx-ddk-um: Drop omap5-sgx-ddk-um-linux package Andrew F. Davis
2019-07-24 19:14   ` Denys Dmytriyenko
2019-07-24 19:30     ` Andrew F. Davis
2019-07-24 20:08       ` Denys Dmytriyenko [this message]
2019-07-24 21:08         ` Andrew F. Davis

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=20190724200834.GH5700@beryl \
    --to=denys@ti.com \
    --cc=afd@ti.com \
    --cc=meta-ti@yoctoproject.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.