Versions in ports

[Artur Szostak]

Then why not protect all other upgrade operations with a -f | --force flag, except when upgrading everything? It seems much too easy at the moment to perform an upgrade operation that has a good chance of leading to an inconsistent state.

________________________________
From: Brandon Allbery [allbery.b at gmail.com]
Sent: 14 September 2015 16:32
To: Artur Szostak
Cc: Macports Users ‎[macports-users at lists.macosforge
Subject: Re: Versions in ports

On Mon, Sep 14, 2015 at 10:22 AM, Artur Szostak <aszostak at partner.eso.org<mailto:aszostak at partner.eso.org>> wrote:
To me, it feels like the MacPorts documentation is misleading the end user to believe that upgrading/downgrading individual packages is a routine and safe procedure, when my experience tells me otherwise. Can anyone point me to the reason behind these design decisions?

I suspect you are reading experience with something like yum or apt-get into a ports-based system. MacPorts gets most of its behavior from BSD ports/pkgsrc, and the documentation tends to assume that you are familiar with that.

--
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com<mailto:allbery.b at gmail.com>                                  ballbery at sinenomine.net<mailto:ballbery at sinenomine.net>
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20150914/3f331847/attachment.html>