All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] pkg-generic: support patching local source code
Date: Fri, 10 Apr 2015 00:12:29 +0200	[thread overview]
Message-ID: <20150409221228.GC4192@free.fr> (raw)
In-Reply-To: <1428539284-5957-1-git-send-email-nic.dade@mistsys.com>

Nicolas, All,

On 2015-04-08 17:28 -0700, Nicolas S. Dade spake thusly:
> Signed-off-by: Nicolas S. Dade <nic.dade@mistsys.com>

Thanks for your patch!

However, we're explicitly not allowing patching local sources, on
purpose.

The use-case for using local sources is to allow people to use a
development version of the package, one they are hacking on. Thus, we
believe that in most cases, the patches bundled with Buildroot would
most certainly fail to apply on local sources.

So, we think that, if those patches are still needed, the developper
will have to carry them in its local sources.

Also, your commit log is not explaining the issue you are facing, so it
is hard to udnerstand why you would need bundled patches to be applied,
and the use-case that would cover.

I'm leaving this open for now, for others to speak up, but I'd be
tempted to say "no" for the aforementioned reasons.

Regards,
Yann E. MORIN.

> ---
>  package/pkg-generic.mk | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/package/pkg-generic.mk b/package/pkg-generic.mk
> index f77aab2..09f2405 100644
> --- a/package/pkg-generic.mk
> +++ b/package/pkg-generic.mk
> @@ -555,15 +555,18 @@ else
>  # In the package override case, the sequence of steps
>  #  source, by rsyncing
>  #  depends
> +#  patch
>  #  configure
>  
>  # Use an order-only dependency so the "<pkg>-clean-for-rebuild" rule
>  # can remove the stamp file without triggering the configure step.
> -$$($(2)_TARGET_CONFIGURE): | $$($(2)_TARGET_RSYNC)
> +$$($(2)_TARGET_CONFIGURE): | $$($(2)_TARGET_PATCH)
>  
>  $(1)-depends:		$$($(2)_FINAL_DEPENDENCIES)
>  
> -$(1)-patch:		$(1)-rsync
> +$(1)-patch:		$$($(2)_TARGET_PATCH)
> +$$($(2)_TARGET_PATCH):	$$($(2)_TARGET_RSYNC)
> +
>  $(1)-extract:		$(1)-rsync
>  
>  $(1)-rsync:		$$($(2)_TARGET_RSYNC)
> -- 
> 1.9.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-04-09 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09  0:28 [Buildroot] [PATCH 1/1] pkg-generic: support patching local source code Nicolas S. Dade
2015-04-09 22:12 ` Yann E. MORIN [this message]
2015-04-09 22:21   ` Nicolas Dade
2015-04-09 22:40     ` Yann E. MORIN
     [not found]       ` <CAB7JjA_EKRS9uEX9MhgUVpovh4VKoUF2vx1wE2Q+a9baZTRyCQ@mail.gmail.com>
2015-04-10 17:30         ` Yann E. MORIN
2015-04-10 21:08     ` Arnout Vandecappelle
2015-04-10 21:31       ` Nicolas Dade

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=20150409221228.GC4192@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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.