On Friday 24 October 2003 02:41 pm, Jesse Guardiani wrote:
> Kent Stewart wrote:
> > On Friday 24 October 2003 01:38 pm, Jesse Guardiani wrote:
> >> Kent Stewart wrote:
> >> > On Friday 24 October 2003 10:41 am, Jesse Guardiani wrote:
> >> > I come from the programming world and to update a library and not
> >> > update the codes that use it really bothers me. I do what you did but
> >> > I keep thinking about all of the problems that I could be causing.
> >> Ah. I see. It's binary compatibility thing. Portupgrade has no way of
> >> knowing if the new package is binary compatible with the old package, so
> >> it builds the new package, uninstalls the old package, and installs the
> >> new one. Grrr...
> >> OK. I guess I'll just have to rebuild my entire ports tree if I want it
> >> done right.
> > Not all of the time. For example, the only one in recent time was the
> > gettext library problem.
> > The other thing is why are you telling portupgrade to recursively build
> > all of grip's dependancies when you may not need to. I look at what
> > portversion tells me is out of date first.
> You mean portupgrade won't recursively upgrade my ports that are out of
> date? It rebuilds ALL of them?
It didn't in the past. You only had to create packages and you would see them
with 1-2 minute differences in creation times. That is only long enough to
re-package the large tarball, which is what I see it doing.
> Hmmm... I never noticed that before. That stinks!
I could be also wrong. When it comes to computers, truth is a sliding window.
> I'm looking for an automated upgrade proceedure here. portupgrade doesn't
> seem to be giving it to me.
You are also looking for a quick solution and that is what portupgrade doesn't
always provide. It can't make the decision of rebuilding what has been
updated versus rebuilding everything is needed. There isn't any magic flag in
the port tree to tell portupgrade that all of the dependant ports need to be
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"