On Tue, 17 Jul 2012 20:51:17 +0200 (CEST) sauer wrote: n> Speaking of the standard library, what are the chances of more n> formally documenting the miniumum version requirement for using that n> file? I updated it recently, and found that I had to comment out a n> few chunks to retain compatability with some older binary versions n> (which, for a variety of reasons, I can't immediately update). It's n> not the end of the world to have to keep commenting parts out, but it n> reminded me that it's never been quite clear what the lifecycle is for n> old releases. :)
The intent is that the current version in Design Center as CFEngine::stdlib will be the last one to lack that specificity. From now on, every new CFEngine::stdlib release that has incompatibilities will cause the old one to be rotated out to CFEngine::stdlib::x_y_z where x_y_z is the last Community version it could use. So if you are above x.y.z you are fine. If not, you use the best one that suits you. I would take patches to add a CFEngine::stdlib::3.?.? to the Design Center that you have verified. I don't know what particular versions you're concerned with, but everyone benefits if we make your knowledge part of Design Center. Ted _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
