It seems like it would potentially be a nice thing for an institution to set
up one master repository, pkg.yourcomany.com, and then allow different
departments to manage their own sections of it, whether for public or
private reasons.
However... I cant seem to find any documentation along these lines.
http://docs.oracle.com/cd/E23824_01/html/E21803
doesnt say much about use of pkgsend. I've had more luck with random pages
on the internet
Unfortunately, there seems to be an actual code level issue in the way of
nice cooperation between publisher areas.
I did a trial run, creating a repo initually as a regular user, with
publisher 'x'.
I then added a file, *as root*, self-described as publisher 'y'
I then tried to update the original file, as a regular user.
Problem....
pkgsend: Could not operate on (home)/testrepo/publisher/y/tmp/lock
because of insufficient permissions. Please try the command again as a
privileged user.
Bug in pkgsend, leaving lock files around?
The really annoying thing is, even if I REMOVE that file... it still
complains about it if I try the pkgsend again.
Am I missing something here, or is it just that no provision has been made
for clean delegation of different publisher areas?
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
