On Tue, 2009-08-25 at 14:52 -0500, Shawn Walker wrote: [...] > The issue of --force and --no-deps is that if you use it 'now' to 'fix' > something that's broken, your system will be forever broken later until > you actually do it right.
Agreed. And I'm not saying that pkg should have --force and --no-deps, but I wonder if ... something ... in that general ballpark might actually make it less likely to have a broken system. For instance, I have a need to build and install the various a11y libs -- and on occasion Gtk+. I cannot remove these packages because so many things depend on them. I've tried making pkg(5) files, placing them in a local repo, and then updating the existing packages with those I've created but, as I recall, packagemanager wouldn't let me update them stating I had to do an update all instead. I don't recall why update all failed now, but it did. So what I wind up doing is taking a snapshot and then overwriting the files with a make install. (Yeah, I know, baaaaad user.) If I catch a screw-up in my build immediately, it's easy to rollback. If I don't catch it for awhile, however, rolling back becomes less ideal. If I could cause packagemanager to remove just the packages I need to overwrite, couldn't I later recover from a broken build by simply reinstalling those packages? I could also re-install those packages right before performing an update so that I'm not asking pkg to update a system which is not in the state pkg thinks it is. Having just thought through the above, I guess what I'd like to see, more than --force and --no-deps is a way to restore the packages whose files I wind up having to overwrite. Take care. --joanie _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
