Shawn Walker wrote:
On 08/17/12 16:29, Philip Brown wrote:
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.
you seem to be somewhat obsessively focused on "[the classes]".
If I write a replacement for pkgsend, I will write it from scratch, purely
to the file spec that you referenced. I wont touch the oddly encumbered
internal python libraries.
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".
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?
Are you basically just saying, "I dont know, I havent looked at the classes
for a long time and it isnt documented anywhere" ?
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
