On Wed, Apr 16, 2008 at 03:28:15AM -0400, Steven M. Christensen wrote: > repository for the x86 Companion CD packages a while back > using solaris.py and it seems to work so far. Now, I have a > number of updates to these packages I want to do. What is the > current best procedure for updating a given package? > > If I want to update the IPSFWxterm package, for example, is it > just > > pkgsend -s http://localhost:9000 send IPSFWxterm
That should do the trick, but note that unlike using solaris.py, you won't get any dependencies calculated. > I saw the "How to replace a package ..." discussion a while back, but > I am not sure that answered this question. Should I just > remove the old repository and replace it using solaris.py again instead > of trying to update packages one at a time? If I do that, will an > end user get the new IPSFWxterm package if the do a pkg install? No, there's no reason to remove the old repository -- you wouldn't want to do that if you were only updating some of the packages, right? Clients will always get the newest version of a package, unless their system constrains them to a lower version, which is unlikely at this point. > 2. Is there a procedure for installing and running two or more separate > repositories on one server? I know I could put all packages in one > repository, but would rather keep, hypothetically, SPARC and x86 > packages in different repositories, say on ports 9000 and 9001 respectively. Just run two different repositories. Either run them by hand and use the appropriate arguments to the -p and -d options, or run two instances of the pkg/server service. You'll need to change the 'port' and 'inst_root' properties in one of them. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
