Re: portmaster is not always recursive

2009-09-08 Thread Doug Barton
Miroslav Lachman wrote: > And now I have one problem on topic with recursive update. > > There were about 50 available updates, but I want to update just p5 > modules for Amavis / SpamAssassin. In this case -a + -i is not so useful > option nor +IGNOREME. There was already a discussion earlier in

Re: portmaster is not always recursive

2009-09-07 Thread Miroslav Lachman
Doug Barton wrote: Miroslav Lachman wrote: I know about -f, but it "always" forces update of dependencies. I mean something "inteligent" to do update of intermediate dependencies only in case when some bottom dependency will be updated. I'm not sure that I'm following exactly what you're as

Re: portmaster is not always recursive

2009-09-07 Thread Doug Barton
Miroslav Lachman wrote: > I know about -f, but it "always" forces update of dependencies. I mean > something "inteligent" to do update of intermediate dependencies only in > case when some bottom dependency will be updated. I'm not sure that I'm following exactly what you're asking for there, but

Re: portmaster is not always recursive

2009-09-07 Thread Miroslav Lachman
Doug Barton wrote: [...] So the last thought is some new option for portmaster to force reinstall of all intermediate dependencies between A and E, even if there are no updates for them. The -f option already does this. Thank you again for you explanation of the problem. It is really educ

Re: portmaster is not always recursive

2009-09-03 Thread Mel Flynn
On Sunday 30 August 2009 19:07:24 Doug Barton wrote: > Ok, I found the problem, but the bad news is that I don't know what the > solution is going to be. I've cc'ed ale since what I'm seeing is weird > behavior by the php5-mcrypt slave port. > > What portmaster does by default when looking for depe

Re: portmaster is not always recursive

2009-08-31 Thread Alex Dupre
Doug Barton ha scritto: >> Does it mean that portmaster checks only first level dependencies >> unless -t is given? (Maybe it is good behavior, I am just asking it to >> be sure that I understand it well) > > That's not exactly right, but it's about 90% right so close enough. :) > The discrepancy

Re: portmaster is not always recursive

2009-08-30 Thread CmdLnKid
On Sun, 30 Aug 2009 16:17 -, dougb wrote: On Sun, 30 Aug 2009, Miroslav Lachman wrote: Doug Barton wrote: Ok, I found the problem, but the bad news is that I don't know what the solution is going to be. I've cc'ed ale since what I'm seeing is weird behavior by the php5-mcrypt slave port.

Re: portmaster is not always recursive

2009-08-30 Thread Doug Barton
On Sun, 30 Aug 2009, Miroslav Lachman wrote: Doug Barton wrote: Ok, I found the problem, but the bad news is that I don't know what the solution is going to be. I've cc'ed ale since what I'm seeing is weird behavior by the php5-mcrypt slave port. What portmaster does by default when looking

Re: portmaster is not always recursive

2009-08-30 Thread Miroslav Lachman
Doug Barton wrote: Ok, I found the problem, but the bad news is that I don't know what the solution is going to be. I've cc'ed ale since what I'm seeing is weird behavior by the php5-mcrypt slave port. What portmaster does by default when looking for dependencies is to run 'make build-depends

Re: portmaster is not always recursive

2009-08-30 Thread Doug Barton
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Ok, I found the problem, but the bad news is that I don't know what the solution is going to be. I've cc'ed ale since what I'm seeing is weird behavior by the php5-mcrypt slave port. What portmaster does by default when looking for dependenc

Re: portmaster is not always recursive

2009-08-29 Thread Doug Barton
Miroslav Lachman wrote: > Doug Barton wrote: >> Miroslav Lachman wrote: >> >> >>> I have another case, where portmaster did not update dependency. >>> >>> I started with the following list of available updates >>> >>> r...@elsa ~/# portmaster fetch update && pkg_version -vIL = >>> apache-2.2.11_7

Re: portmaster is not always recursive

2009-08-29 Thread Miroslav Lachman
Doug Barton wrote: Miroslav Lachman wrote: I have another case, where portmaster did not update dependency. I started with the following list of available updates r...@elsa ~/# portmaster fetch update && pkg_version -vIL = apache-2.2.11_7 < needs updating (index has 2.2.13)

Re: portmaster is not always recursive

2009-08-29 Thread Doug Barton
Miroslav Lachman wrote: > I have another case, where portmaster did not update dependency. > > I started with the following list of available updates > > r...@elsa ~/# portmaster fetch update && pkg_version -vIL = > apache-2.2.11_7 < needs updating (index has 2.2.13) Portmaster d

Re: portmaster is not always recursive

2009-08-29 Thread Miroslav Lachman
Doug Barton wrote: Miroslav Lachman wrote: [...] I can confirm that bug was fixed in 2.10, it passed my test with -r jpeg-7 ;) Also good news. :) I'm actually pretty confident at this point that this bug was the cause of most, if not all of the "oops, portmaster missed a dependency update

Re: portmaster is not always recursive

2009-08-21 Thread Doug Barton
Miroslav Lachman wrote: > Doug Barton wrote: >> Unfortunately it didn't quite keep up with the times when some code >> paths were added (such as -r and the new code to do multiple ports on >> the same command line) and it was not always being unset when it >> should have been. The more common code

Re: portmaster is not always recursive

2009-08-21 Thread Miroslav Lachman
Doug Barton wrote: Woo hoo! I found the bug, and fixed it in the just-committed version 2.10. The bug was in the NO_DEP_UPDATES flag which is one of the oldest features of portmaster. It operates in the first pass through the dependencies (aka config mode) and if all of the dependent ports are up

Re: portmaster is not always recursive

2009-08-20 Thread Doug Barton
Woo hoo! I found the bug, and fixed it in the just-committed version 2.10. The bug was in the NO_DEP_UPDATES flag which is one of the oldest features of portmaster. It operates in the first pass through the dependencies (aka config mode) and if all of the dependent ports are up to date it allows th

Re: portmaster is not always recursive

2009-08-19 Thread Miroslav Lachman
Doug Barton wrote: Miroslav Lachman wrote: Doug Barton wrote: Miroslav Lachman wrote: [...] I have seen similar problem in the past with amavisd-new + spamassassin and their dependencies, but it is much bigger and complicated tree of dependencies and I have not evidence recorded for it.

Re: portmaster is not always recursive

2009-08-19 Thread Miroslav Lachman
Doug Barton wrote: Miroslav Lachman wrote: Doug Barton wrote: Miroslav Lachman wrote: [...] I have seen similar problem in the past with amavisd-new + spamassassin and their dependencies, but it is much bigger and complicated tree of dependencies and I have not evidence recorded for it.

Re: portmaster is not always recursive

2009-08-18 Thread Doug Barton
Miroslav Lachman wrote: > Doug Barton wrote: >> Miroslav Lachman wrote: > > [...] > >>> I have seen similar problem in the past with amavisd-new + spamassassin >>> and their dependencies, but it is much bigger and complicated tree of >>> dependencies and I have not evidence recorded for it. >>> R

Re: portmaster is not always recursive

2009-08-18 Thread Miroslav Lachman
Doug Barton wrote: Miroslav Lachman wrote: [...] I have seen similar problem in the past with amavisd-new + spamassassin and their dependencies, but it is much bigger and complicated tree of dependencies and I have not evidence recorded for it. Reported case with jpeg / gd / png is the simple

Re: portmaster is not always recursive

2009-08-17 Thread Doug Barton
Miroslav Lachman wrote: > Doug Barton wrote: >> Miroslav Lachman wrote: >> >>> Hi, >>> >>> I have some problem with portmaster. >>> If I do upgrade of graphics/gd, portmaster check and upgrade all >>> dependencies of gd (png, jpeg, pkg-config, freetype) but if upgrade of >>> gd is called by upward

Re: portmaster is not always recursive

2009-08-17 Thread Miroslav Lachman
Doug Barton wrote: Miroslav Lachman wrote: Hi, I have some problem with portmaster. If I do upgrade of graphics/gd, portmaster check and upgrade all dependencies of gd (png, jpeg, pkg-config, freetype) but if upgrade of gd is called by upward recursive upgrade of jpeg library, I end up with ne

Re: portmaster is not always recursive

2009-08-17 Thread Doug Barton
Miroslav Lachman wrote: > Hi, > > I have some problem with portmaster. > If I do upgrade of graphics/gd, portmaster check and upgrade all > dependencies of gd (png, jpeg, pkg-config, freetype) but if upgrade of > gd is called by upward recursive upgrade of jpeg library, I end up with > new jpeg, n

portmaster is not always recursive

2009-08-17 Thread Miroslav Lachman
Hi, I have some problem with portmaster. If I do upgrade of graphics/gd, portmaster check and upgrade all dependencies of gd (png, jpeg, pkg-config, freetype) but if upgrade of gd is called by upward recursive upgrade of jpeg library, I end up with new jpeg, new gd, new mrtg, but old png. It m