On 08/17/12 14:34, Philip Brown wrote:
...
This was a test of doing a pkgsend publish, of one specific package, for
one specific publisher. A single command line "pkgsend publish blahblah..."
Okay, it touches some top level things, such as pkg5.repository
And okay, it touches a bunch of files under the publisher specific area,
such as files under /index/ and /catalog/
But then it goes and looks at the same files under the index, and
catalog, directories, of EVERY OTHER PUBLISHER
This is very wrong :(
I'm not sure where you get "wrong". A repository is not intended to be
a loose container that manages isolated sets of publisher data.
Instead, it is managed as a container that manages multiple sets of
publisher data.
In short, when a user points at a repository, some very minimal
validation of layout of the top level of each publisher and status is
necessarily performed to ensure that we don't use a repository that is
partially corrupt or invalid.
The behaviour that is there is intentional. That isn't to say that it
couldn't be changed, but in this particular case, the overhead of the
operations you saw should be very minimal unless you're severely I/O-bound.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
