On Tue, Apr 7, 2015 at 7:52 AM, Ed Bartosh <ed.bart...@linux.intel.com> wrote: > 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.
There are several solutions for this very same problem. Each one has advantages or disadvantages. To be honest, I think we ought to focus in making wic more easy to use and robust right now. Later we can think about how to enable side use cases (Buildroot might be one). -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
