On 08/17/12 16:29, Philip Brown wrote:
Shawn Walker wrote:
Please reference the design document for the current repository format:
http://src.opensolaris.org/source/xref/pkg/gate/doc/on-disk-format.txt
The top-level of the repository is intended to be able to hold a
shared file storage area that crosses publisher boundaries to reduce
storage requirements for specific use cases.
Thank you for the reference.
Perhaps, if I can manage to find the time, I shall write a replacement
for pkgsend that is not constrained by these "specific use cases".
And again, pkgsend is not the manager of behaviour here. The internal
package repository class is.
The pkg5.repository file itself is intended to contain metadata that
can drive both pkg.depotd and potentially client behaviour as a whole,
so is necessarily centralised instead of per-publisher.
Is there any documentation for what locking, if any, pkg.depotd uses?
No; pkg.depotd itself does not do the locking.
As I've repeatedly stated, all locking is performed by internal classes;
not by the programs that manipulate the repository.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
