Library packs
A pack is a consistent, versioned set of libraries, reusable from one project to another and shareable with a group. It is the only way to save libraries: there is no save button on the library pages themselves.
Everything happens in Management → Backup & Sharing.
Create a pack
Creates a full pack from the libraries currently used by the project: name, description, families to include and location.
Prerequisite
A pack only captures what the project has customized. If no library has been modified in the project, creation is refused: modify and save at least one library first.
Apply a pack
The Use button applies the pack to the current project.
What is not overwritten
Libraries already copied and modified locally in the project are not affected. Applying a pack therefore never destroys work in progress — but it also means a pack does not overwrite an existing customization.
Manage packs
| Action | Effect |
|---|---|
| Update | Re-saves the pack with the project's current libraries, creating a new version |
| Rename | Changes the label |
| Duplicate | Deep copy — the new pack is independent of the original |
| Version history | Lists previous versions, with the option to restore |
| Publish to a group | Copies the pack to a group you administer, for its members |
| Detach | Detaches the project from the pack. The pack is not deleted, the applied libraries stay in place |
| Delete | Deletes the pack. Libraries already copied into projects are not affected |
Publishing = recopying
Publishing to a group recopies the libraries: the published pack stays unchanged even if you later modify your own. Same principle as duplication — the independence is deliberate.
Versions and pointers
A pack points to a specific version of each library. If a pointed-to version has been purged, the application falls back to the most recent available version and informs you explicitly, library by library.
Private server
Limitation on private storage
For a project hosted on a private server, creating and updating a pack are not available. Still possible: switching packs, and using an already retrieved pack.
The Copy to private server button retrieves a pack from the VPS into the private server's local cache.
See also
Manage libraries for the principle of families, sources and the frozen copy in the project.