----- Original Message -----
>
> Adding more features isn't really on the roadmap at all anymore AIUI,
> saying that I'd assume the code would be much more LVM heavy than yum
> heavy, esp. now the first version is done ... so the parts you'd need
> generic yum advice on (or to have a yum person write) should be fairly
> small.
Ok. So, any objections to the high level plan of:
1) Keep the yum configure options of:
fssnap_automatic_{pre,post}
2) Move most of the logic out to roller-derby, and have yum simply
do subprocess.call(["roller-derby", ...])
3) Remove the options "fssnap_automatic_devices", and delegate that
to roller-derby (which might in turn use lvm tags as opt-in/out)
This is all somewhat messy of course, but as you said, I think in
the end this is more LVM management than yum, and it'd be more
clear to admins as a separate tool.