Alan Coopersmith wrote: >>>> Also, why would you need to parse the output? >>> How else does the script know what packages to reinstall afterwards >>> so that upgrade-X doesn't leave the system without GNOME, Java, etc? >> Ah, I was assuming that you would rely on the dependencies to reinstall >> these. > > On what dependencies? I can't just install every package that depends
I (mistakenly?) assumed that if you uninstalled the "key" packages you are replacing (recursively) and then reinstalled just those "key" packages, that any other packages you had replaced that they depended upon would also be reinstalled. I suppose it all depends on what the dependency tree looks like for the set of packages involved. > on libX11 - that will probably include hundreds of new packages that weren't > previous installed. I can run 'pkg contents -o pkg.name,action.raw -t > depend' > and parse that output and do my own recursive descent, but I thought you were > suggesting I could use pkg uninstall -rvn to do the recursive descent and > produce that list for me. I believe you should be able to do that, yes. >> Maybe we need an /alpha repository in addition to the /dev repository? > > Except we need them for each project, because in my world, the SUNWxorg-server > package you download from the vconsoles project will be different than the one > I'm putting out for the Xorg-1.5 upgrade project. In the ON world, I expect > it's more like dozens of projects under parallel development, and you'd want > different bits from the Crossbow, ZFS-Crypto, etc. builds, which may have > the same version number and timestamps that make one look like a newer build > of the other when it's not. That's outside the scope of my experience, so I'll let someone else answer that. > It'd be especially nice if I could have my > pkg.opensolaris.org/projects/xorg-1.5 > repo be a "overlay" of pkg.opensolaris.org/devel, with only the dozen packages > I need to replace in it, and all dependencies and other packages pulled from > the > main one, but even just a simple repo management webapp (similar to the SCM > management webapp being rolled out for projects) that let me set up a new > project repo by cloning /devel and then pkgsend'ing the changed packages would > be awesome. If you setup your own repository with just the packages you want to change in it, and set the corresponding authority as preferred, it should work just like you describe. In other words: pkg authority AUTHORITY URL opensolaris.org http://pkg.opensolaris.org:80/ mypackages (preferred) http://localrepo:port/ ...if you setup the above, the "changed" packages will be pulled from mypackages, and the rest from opensolaris.org. So you don't really need to clone an existing repository. -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
