gonna spitball an idea here... should lenses be packaged separately? would then be easier to cut a release based on added lenses rather than wait for 'stable' updates to the main code. Of course, bearing in mind that sometime there would be versioned dependency between the two.
On Fri, Oct 31, 2014 at 12:36 PM, David Lutterkort <[email protected]> wrote: > Hi Rich, > > On Fri, Oct 24, 2014 at 8:29 AM, Richard W.M. Jones <[email protected]> > wrote: > >> Is it possible that Augeas could make a new tarball release soon? >> > > Yes, I'll try and get a release together next week Friday. > > >> Libguestfs is currently carrying around two lenses (upstream in >> Augeas, but not released), and this causes conflicts if either of >> those lenses is added to a downstream package (as has been done in >> RHEL 7.1). And by "conflicts" I mean it breaks major features of >> tools like virt-sysprep & virt-customize & more. >> > > Is there something that Augeas could do to help at least spot such issues > sooner ? We've talked in the past about some sort of annotation to indicate > lens compatibility, but that never went anywhere. > > Is the breakage simply due to the fact that the upstream enses produce a > tree that's different from the one that the virt-* tools expect ? > > David > > > _______________________________________________ > augeas-devel mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/augeas-devel >
_______________________________________________ augeas-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/augeas-devel
