Allow a Package configuration to be exported/imported

[GoogleCodeExporter]

Something like exporting from a Library, we need an export/import function for 
Packages.

We do note, of course, that Packages rely on many other components that could 
make it less portable than the contents of a Library. That is, it will likely 
have lots of issues if components do not have the same name on the importing 
system as they did on the exporting system, so it'll work best if the the 
contents of the Library were also exported from the same source system.  

The import function will likely need to use some existing Package as the source 
for the imported package to provide permissions and the library name where the 
documents are likely to be stored (as the library on the source and destination 
systems are unlikely to have the same name).

Original issue reported on code.google.com by yoz...@gmail.com on 26 Feb 2013 at 6:58

[GoogleCodeExporter]

Original comment by yoz...@gmail.com on 4 Mar 2013 at 7:38

• Changed state: Started
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Added to release 13.3.9

Original comment by yoz...@gmail.com on 6 Mar 2013 at 9:15

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****