Danek Duvall wrote:
Danek Duvall wrote:
So clearly we need a better story for getting off a private or project repo
for the simple cases when you haven't diverged "too far". You shouldn't be
punished for having taken a couple of packages off the beaten path, but if
you take most of your system, well, maybe that can be a bit harder. Still,
if we can make it easy to come back, we should.
An idea occurred to me that you might want to try if you're still in a mood
for experimentation.
Republish the package that you want to replace, empty of contents, except
for a dpendency on a new package, which has the contents and version that
you want. This is effectively renaming the old package name to the new.
I've actually done this about 6 months or so ago.
The lame package in the /pending repository had a dependency on an
ncurses package that didn't exist in any or /pending /contrib /dev or
/release. However there was a SUNWncurses package in /dev.
So I published a package in my local repo called ncurses that all it had
was a dependency on SUNWncurses. That was sufficient to thet the lame
package installed.
The advantage is that when you do your upgrade, your renamed copy of the
package would be upgraded to the WOS version (modulo the authority
"jumping" behavior I'd mentioned previously). This might not actually be
an advantage if your version is way ahead and you want to keep it that way.
I don't believe I attempted upgrade on that system so I don't know how
that would have worked out - it has since been rebuilt from scratch though.
--
Darren J Moffat
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
