Macports does what I want (?) not what I say
jonesc at hep.phy.cam.ac.uk
Thu Jul 4 06:54:17 PDT 2013
>> Because they are direct or indirect dependencies of the port you asked to install or upgrade.
> But there is really no need to upgrade them, they already satisfy the dependency. This wasn't even too bad, after all, when I hit gtk I want to cry.
oh but there is a need to upgrade all dependencies. Often changes are
introduced into ports that require updates in dependant ports, so both
have to be committed at the same time. If you then where able to update
one, without the other you would get a broken system which is why this
is not something that is at all recommended.
Why do you care so much about how many updates come in ? Have you
disabled binary packages, kin which case you will not have to build most
yourself (a few still have to be for various reasons). With binary
packages, updates are quick and painless, so why care.
>>> Is there any way I can restore the previous behaviour both in regards to upgrading dependencies and upgrading when I say install?
>> MacPorts has always first upgraded dependencies of the ports you asked to install or upgrade. Not doing so would be completely counterproductive to the way that MacPorts is designed to work. We will not help you attempt to circumvent a fundamental functionality of MacPorts, because it would likely increase our support burden when you do this and then ask us why things aren't working right.
> Maybe I mistook a very old bug (in the ports if not in macports, I'm sure it happened) for a feature, but I really liked it. I assume from your answer that there is no intention whatsoever of implementing a >= check for dependencies versions. It doesn't sound so unreasonable to me, but then again I'm not the one developing it...
>>> I'd really love to have back a tool that does what I say not what it believes I want.
>>> I already put this into my aliases
>>> port='port -cn'
>>> but it obviously doesn't work.
>> -c is autoclean mode which is the default; you do not need to specify it.
>> -n is don't-upgrade-dependencies mode; please don't attempt to use that on a regular basis; it's meant for special situations only.
> I promise I will not come back crying before removing the option and re-updating everything, but I just can't stand hours of compilation on my tiny cpu while I'm working. I'll try to schedule over-weekend updates for the dependencies...
> Thanks for the feedback
> macports-users mailing list
> macports-users at lists.macosforge.org
More information about the macports-users