On Mon, Apr 28, 2008 at 12:24:52PM +0200, Alexander Vlasov wrote: > I have a few usecases/common scenarios and currently I can't understand > how they should be processed with IPS. Can anyone point me to > appropriate docs or just explain me the correct way of doing this stuff?
None of this is possible at the moment. > 1. > Company X has internal repository for employees and external repository > for community. How can admin copy packages X and Y to public repository? > Any easy way of copying package from one repository to another without > pulling to third machine and pushing back to second repository? We're in the process of writing a tool that allows for republication like this. I don't believe it's a server-to-server copy yet, though. > 2. > Company Y has repository available o all employees, but only some of > them are allowed to push packages there (say, developer staff). How can > this be achieved? As far as I understand, repo is either read-only or > volatile. > > 3. > Company Z has different versions of their product. Any client should > gain access only to appropriate part of repository. How can this be > achieved? Client access will be limited using client-side certificates. You'll be able to set up authorizations based on the certificates to allow access to certain portions of the server. Publication authorization could be handled that way, too. > 4. > Package A considered buggy and should be removed from repository. Any > way of doing this? Not yet. Though you could publish a new package with the same name, but no contents. Anyone who installs that version will get nothing, and anyone who upgrades will have all the bits of the original version removed. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
