Re: [devtool][PATCH] devtool deploy-target: optionally specify package

[Trevor Woerner <twoerner@gmail.com>]

Hi Paul,

I was hoping you'd notice and provide feedback :-D

On Tue 2018-06-05 @ 10:59:07 AM, Paul Eggleton wrote:
> > I checked at the time, but I'm not 100% sure now, but I believe if one
> > deploys two packages from one recipe, the on-target file gets appended. But
> > now I'm not 100% sure, so I'll verify this tomorrow (thanks for the
> > reminder). 
> 
> The way I recall writing it, it will remove whatever it deployed last time, so 
> I would be surprised if it were incremental.

Yes, further investigation demonstrated this to be the case. This is a good
feature, since it handles the case where files or filenames might change
between deployments.

I've since updated the patch (locally) so that the on-target filenames of the
deployments, e.g. <recipe>.list and <recipe>.preserve, now include the
optional packagename (if this option is used): e.g. <recipe>.<package>.list
and <recipe>.<package>.preserve. In this way a user can deploy and undeploy
multiple packages from the same recipe independently of each other without any
of them clobbering the other.

The only caveat, now, would be if the user then deployed the entire recipe. In
this case the on-target files would still be the things the user was working
on; the "problem" would be an inconsistency in the on-target devtool
accounting files. In other words, it would be inadvisable to mix and match
between using and not using the --package option within the same recipe.

Best regards,
	Trevor