Frans Lawaetz wrote:
> I see your point however this is the existing behavior of the community
> RPMs.
>
> # rpm -ql cfengine-community | grep -c /usr/local
> 247
>
> If nothing else I would appreciate having the post-install logic ensure that
> binaries are successfully placed in /var/cfengine/bin. The bug resulted in
> an upgrade where *no* cfengine binaries were present.
>
Sorry for the delay in responding. I realized I had the details of your
change backward and decided to take a break.
I see your point. RPMs that remove binaries and don't install the
replacements are not useful. (The whole episode raises some interesting
ideas for RPM quality checking and regression testing.)
Should we actually have the binaries in /usr (to follow RPM conventions)
and symlinks from /var/cfengine/bin (since that's where cfengine
conventions would put them)? Or has Mark issued a policy statement
about whether the community binaries should follow the packaging system
conventions or the cfengine conventions?
Regards,
Richard Siddall
(Hoping I'm more lucid this morning.)
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
