I maintain two projects that are basically the same, one for Development
and one for Production. They're not quite the same, though, as some
things that I do in production (like sending email to our security
department) shouldn't happen in development (to keep from annoying them
while I'm testing something). I'm making extensive use of Library objects
to hold shared policies for multiple drivers. And I just discovered that
a bunch of my "development" versions of library policies are actually in
"production".
I figured out how this happened. Export to config file and Import from
config file silently updates the library.
As an example:
In my Development project I have Driver A with policy X in the library,
and Driver B with policy Y in the library.
In my Production project I have Driver A with policy X in the library. I
do not yet have Driver B, because I'm working on it still.
Policy X in Development is _different_ from Policy X in Production. It
doesn't matter how it's different, only that it be somehow different. A
comment, a disabled rule, anything will do.
Export Driver B from the Development project. Because it has links to
policies that are not local to it, you're prompted for exporting the
externals as well. If you say "no", then only polices local to Driver B
are exported. But if you say "yes" here, then the linked policy Y is
exported. Answer "yes" to this prompt. But Designer can't export just a
policy, it exports all of the library. This includes Policy X, even
though it has nothing to do with Driver B.
Now Import Driver B from the config file. The library Policy X will be
updated silently from the config file. The "Development" version of
Policy X has just snuck in to the "Production" project.
https://bugzilla.novell.com/show_bug.cgi?id=548558
--
---------------------------------------------------------------------------
David Gersic
dgersic_@_niu.edu
Novell Knowledge Partner
http://forums.novell.com
Please post questions in the newsgroups. No support provided via email.