From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v0] Add support for automated building of Opkg repository
Date: Thu, 17 Jan 2013 11:23:17 +0100 [thread overview]
Message-ID: <1423867.kLX9PqGxu5@sagittae> (raw)
In-Reply-To: <1358268430-2431-1-git-send-email-jezz@sysmic.org>
On Tuesday 15 January 2013 17:47:07 J?r?me Pouiller wrote:
> Dear,
>
> I wrote a first draft of support of building deb or ipk file in Buildroot.
> The result looks like this:
> http://sysmic.org/~jezz/ipk_repository
>
> This patch use inotify to spy which file are installed by package. Once
> installation is done, it copy file to a temporary directory where ipk file
> is built.
[...]
> Result is not so bad, as you can see on URL above and it is not intrusive. I
> would be glad to get your opinion about this work. What do you think about
> it?
[...]
Hello all,
I am surprised to have any reply to this patch proposal. Patches have been
correctly sent? (I didn't receive them but I am sure it come from my local
mailer daemon since they appear on gmame). Or I am just too impatient?
I would like to know if some of you think this feature is interesting/useful?
And do you think I take the right way?
Regards,
--
J?r?me Pouiller
next prev parent reply other threads:[~2013-01-17 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 16:47 [Buildroot] [PATCH v0] Add support for automated building of Opkg repository Jérôme Pouiller
2013-01-15 16:47 ` [Buildroot] [PATCH 1/3] Add an entry in images sub-menu for ipk repository building Jérôme Pouiller
2013-01-15 16:47 ` [Buildroot] [PATCH 2/3] Add main scripts for opkg " Jérôme Pouiller
2013-01-15 16:47 ` [Buildroot] [PATCH 3/3] Add parsing of Config.in in ipk-post.sh Jérôme Pouiller
2013-01-17 10:23 ` Jérôme Pouiller [this message]
2013-01-17 12:54 ` [Buildroot] [PATCH v0] Add support for automated building of Opkg repository Thomas Petazzoni
2013-01-17 14:39 ` Jérôme Pouiller
2013-02-13 21:43 ` Carsten Schoenert
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=1423867.kLX9PqGxu5@sagittae \
--to=jezz@sysmic.org \
--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