From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [wic][PATCH] wic: extended list of paths in find_binary_path
Date: Tue, 7 Apr 2015 13:52:22 +0300 [thread overview]
Message-ID: <20150407105222.GA19725@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKqL_fwFw_zD4jBBNqjYg=kgeQC5scV+0paMhkO9XOmf0A@mail.gmail.com>
On Mon, Apr 06, 2015 at 11:28:24AM -0300, Otavio Salvador wrote:
> >>
> >> If we want to have it as a 'standalone' tool we will need to somehow
> >> package the tool set for it to use, otherwise we have a maintenance
> >> nightmare (does patch X has been applied to Parted?).
> >>
> > Can you elaborate a bit on how tool set can be packaged?
>
> We could do a tarball like the buildtools toolchain.
I was thinking about providing wic and its dependencies as repository with rpm/deb packages.
Providing them as a tarball doesn't differ much from what we already have from my point of view.
--
Regards,
Ed
next prev parent reply other threads:[~2015-04-07 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 17:20 [wic][PATCH] wic: extended list of paths in find_binary_path Ed Bartosh
2015-04-04 18:34 ` Otavio Salvador
2015-04-04 21:34 ` Ed Bartosh
2015-04-05 19:13 ` Philip Balister
2015-04-06 17:43 ` [wic][PATCH] wic: use native parted Ed Bartosh
2015-04-06 18:20 ` Otavio Salvador
2015-04-05 19:16 ` [wic][PATCH] wic: extended list of paths in find_binary_path Philip Balister
2015-04-06 12:00 ` Otavio Salvador
2015-04-06 14:15 ` Ed Bartosh
2015-04-06 14:28 ` Otavio Salvador
2015-04-07 10:52 ` Ed Bartosh [this message]
2015-04-07 11:23 ` Otavio Salvador
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=20150407105222.GA19725@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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