public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/2] Add basic patch support
Date: Wed, 21 Feb 2018 10:36:01 +0100	[thread overview]
Message-ID: <9106ed79-3d3d-f485-a551-deca62862804@siemens.com> (raw)
In-Reply-To: <4a2e08c0-a483-3469-2466-1aadbc51218c@ilbers.de>

On 2018-02-20 12:12, Alexander Smirnov wrote:
> On 02/18/2018 10:39 PM, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Add a do_patch task after unpack the processes .patch files in the
>> SRC_URI. We likely miss some special features compared to OE, but this
>> covers the common case of few individual patches. Application order is
>> derived from appearance in SRC_URI list. Strip level can be configured
>> via "striplevel=N" URI parameter. The application is controlled
>> explicitly via the "apply=yes|no" parameter.
> 
> What's the issue to take the full implementation from OE? How this
> user-interface differs from OE?

The OE version is much more complex, consisting of a class + some
library code at least. The library code seems to have further
dependencies on OE functions. Importing all that, possibly changing
things to work again, requires some clear maintenance/synchronization
strategy. TBH, that appeared too complex to me at this point, and so
went for the simpler solution. That does not exclude enhancing/replacing
this later on, specifically as this implementation here is compatible
from user-perspective.

Jan

      reply	other threads:[~2018-02-21  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-18 19:39 Jan Kiszka
2018-02-18 19:40 ` [PATCH 2/2] example-app: Add two patches for demonstration and testing purposes Jan Kiszka
2018-02-20 11:12 ` [PATCH 1/2] Add basic patch support Alexander Smirnov
2018-02-21  9:36   ` Jan Kiszka [this message]

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=9106ed79-3d3d-f485-a551-deca62862804@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox