Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Viallard Anthony <viallard@syscom-instruments.com>
To: buildroot@busybox.net
Subject: [Buildroot] QUILT helper
Date: Mon, 18 Feb 2013 12:40:27 +0100	[thread overview]
Message-ID: <5122132B.5000402@syscom-instruments.com> (raw)
In-Reply-To: <7241967.ZJo92yCnzW@sagittae>

On 14. 02. 13 17:53, J?r?me Pouiller wrote:
>
> A way to work with patches for a package is currently:
>    make $PKG-dirclean
>    make $PKG-extract
>    cd build/$PKG-$PKG_VERSION
>    git init
>    git add .
>    git rm --cached .stamp_*
>    git commit -m 'initial tarball'
>    git tag initial
>
> After that, import all relevant patches using
>    git am $PATCH
> or
>    git apply $PATCH
>    git commit -a -m "$PATCH"
> depending of format of $PATCH
>
> After that, you may create manually files .stamp_patched and
> .applied_patches_list
>
> Use git rebase to edit each patch. Once you are satisfied, use
>    git format-patch initial
>
> Copy your work in package/$PKG directory
>
> IFAIK you may also use guilt on top of git. Guilt which have nearly same
> commands than quilt. Use "guilt push/pop/refresh" instead of rebase and "guilt
> export" instead of "git format-patch".
>
> We could add an option to apply-patches.sh to automatically do first steps. We
> could do:
>     make $PKG-dirclean
>     make CREATE_GIT=1 $PKG-patch
>     cd build/$PKG-$PKG_VERSION
>     git rebase -i
>     git format-patch initial
>
> And with guilt:
>     make $PKG-dirclean
>     make CREATE_GIT=1 $PKG-patch
>     cd build/$PKG-$PKG_VERSION
>     guilt push/pop/refresh
>     guilt export
>
> What do you think about it?
>

Hello J?r?me,

I think using QUILT directly will be the best. Because, we don't need 
git here. We just need a buildroot system to init quilt env, copy 
patches and when the job is done, copy the patches from quilt env to the 
package directory.

I want so much this feature ! I'm the only one here :) ?

I began to do some research about how openwrt do that and how we can do 
this in buildroot. But, I'm pretty busy and don't have time to do it 
now. If someone who know internal stuff in buildroot can tell where to 
do the modifications, it will be appreciable.

Cheers,
avd.

  reply	other threads:[~2013-02-18 11:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 11:18 [Buildroot] QUILT helper Viallard Anthony
2013-01-19 16:36 ` Arnout Vandecappelle
2013-02-14 16:53   ` Jérôme Pouiller
2013-02-18 11:40     ` Viallard Anthony [this message]
2013-02-18 18:07       ` Arnout Vandecappelle

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=5122132B.5000402@syscom-instruments.com \
    --to=viallard@syscom-instruments.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox