Shawn et al.,
I tried another experiment:
-> set /dev as the only package authority for pkg.
-> pkg uninstall SUNWruby18
-> pkg install SUNWruby18
I expected that this would uninstall the b101 Ruby, and pull the b110
Ruby from /dev. But pkg somehow just wants to go to the release repo
even though I ask it to 'forget' about the release repo.
Is there a way for me to make pkg use only the dev repo?
If so, this would solve my problem. I know I asked specifically about
"updating" and not a uninstall/clean install of a newer version, but
this workaround would probably work for Ruby users too.
(They'd have to set their GEM_HOME to be a path that doesn't lie in the
package's root directory, so as not to lose their gem data during
uninstall - but this is not much of a restriction given that most people
won't use the system gem home anyway).
thanks
-ps
Shawn Walker wrote:
Prashant Srinivasan wrote:
Shawn Walker wrote:
Install only shows packages you *can* install given the constraints
in place. So, the message was correct.
IPS can already update individual packages today. However, the
*packages* as they are currently published are constrained to not
allow you to update between builds.
I see. So there is likely some logic in pkg to ignore requests to
update SUNW* packages individually, or there is (more likely) a
No.
packaging instruction that ties down a package as non upgradeable . .
. or something similar?
Yes, basically. As Danek mentioned, there's a special package called
"entire" that restricts the versions of all of the other packages on
your system. It basically keeps your system from breaking by ensuring
that different pieces don't get upgraded to different versions.
Cheers,
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
