On Mon, 2016-10-10 at 01:44 -0500, gm...@reliableembeddedsystems.com

A few notes (not picking on this patch but it does point out some
design failures and I want to at least get this on folks radar).

I've been unhappy with how DeployArtifacts work for sometime.

Long ago, when I wrote DeployArtifacts, it was "get it working, we'll
refactor later" and that refactor never happened. So I'm up for ideas.

I would like a deploy infrastructure that:

a. Is distro/image name/etc agnostic (aka, poky and image names and
paths hardcoded. ick.).
b. Is perhaps config file driven.
c. Had much less of the cruft that exists withing DeployArtifacts.

So. Thoughts on this? I'd be willing to hear suggestions on how to do
this before I go and spend some time ripping this apart post release?


Beth 'pidge' Flanagan <pi...@toganlabs.com>

yocto mailing list

Reply via email to