Hello,
I had noticed the "computing dependencies for" at the beginning of an
install of upgrade when it first started appearing in 1.8.0. It made
sense which is why I thought it was a good idea and did not mention
it; but, I had not seen the second reference before 1.8.2 which is why
I asked. The reason for noticing is that I sometimes glance over to
the Terminal window to see what is being upgraded and to what version
from what version. It was also mentioned in an earlier posting that
when upgrading dependencies that a test be made to test for "dependent
on" which is different than "dependent for" and wondering if the
suggestion had been acted upon using the wrong wording. It is not a
problem, just an observation.
On Jan 6, 2010, at 4:17 AM, Joshua Root wrote:
On 2010-1-6 13:50 , Frank J. R. Hanstick wrote:
Hello,
I noticed the following change in the port installation procedure:
---> Computing dependencies for apr
---> Fetching apr
---> Verifying checksum(s) for apr
---> Extracting apr
---> Applying patches to apr
---> Configuring apr
---> Building apr
---> Staging apr into destroot
---> Deactivating apr @1.3.9_0
---> Computing dependencies for apr
---> Installing apr @1.3.9_1
---> Activating apr @1.3.9_1
---> Cleaning apr
namely, the extra Computing dependencies for ___. Is this suppose to
be happening or is the second computation for something different
that
the first such as computing dependency on ___?.
I take it this is from an upgrade rather than an install. The message
has been printed since 1.8.0 and mportdepends has been run twice since
probably when the upgrade action was first added. Just an artefact of
how the upgrade procedure works.
- Josh
Frank J. R. Hanstick
[email protected]
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
