On 08/17/12 13:25, Philip Brown wrote:
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?
No; pkgsend itself doesn't create any lock files for the repository.
Any lock files that do exist are temporary files used by the Repository
class internally. The lock file was left behind intentionally (or more
specifically, no need was anticipated for its removal). The presence of
the lock file itself does not define the lock; rather a lock obtain
using fcntl.lockf() on the lock file that only exists for the life of a
process (or until an explicit unlock) is used.
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?
At this time, there is no provision or support for delegation or control
of repository access of any kind. While there may be separate publisher
areas, some repository data is shared between all publishers and must be
writable by anyone manipulating the repository. The separate publisher
directories you see are not actually separate repositories.
-Shawn
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
