On 08/17/12 16:52, Philip Brown wrote:
Shawn Walker wrote:
On 08/17/12 16:29, Philip Brown wrote:
...
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.
This is not a useful nitpick. To nitpick at your nitpicking: that sort
of thing is only useful when it adds value. That's about equivalently
useful as replying to a question of "what files does it open?" by saying
"pkg.depotd doesnt open any files: libc.so does".
Statements were made that implied that end-user programs were
responsible for the locking mechanism or somehow controlled how locking
was performed. They do not. That is why it is a useful nitpick.
It doesnt matter which sub(sub/sub)routine actually does the action...
the important thing is, what kind of locking, etc. does pkg.depot
actually expect when run?
pkg.depotd doesn't expect anything; it merely calls the interfaces
provided and expects the interfaces to handle things such as locking as
appropriate.
Are you basically just saying, "I dont know, I havent looked at the
classes for a long time and it isnt documented anywhere" ?
The details of the locking mechanism are an internal implementation
artefact and so are not documented. The implementation of the locking
mechanism has changed several times although I am aware of the details
of its current implementation.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
