Date: Sat, 16 Jan 2010 14:51:28 -0500 From: Jerry <gesbbb@yahoo.com> To: freebsd-questions@freebsd.org Subject: Re: Dislike the way port conflicts are handled now Message-ID: <20100116145128.32fdd7f0@scorpio.seibercom.net> In-Reply-To: <4B5210F7.9060909@joseph-a-nagy-jr.us> References: <d873d5be1001161001i5d398205hea3d2ec1978ee3f@mail.gmail.com> <20100116190120.GA59663@guilt.hydra> <4B5210F7.9060909@joseph-a-nagy-jr.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Jan 2010 13:18:15 -0600 Programmer In Training <pit@joseph-a-nagy-jr.us> articulated: > That does nothing for conflict resolution, though. That's a big > concern for me because in the past, only one distribution of Linux > (not having used any of the BSD's before, cannot comment on them > except for what I'm seeing in this discussion) that I've used seems > to handle not only package dependency with ease and grace, but also > conflict resolution (in the sense that the only time I've had an > issue with conflicts was when an updated package wasn't available or > an older required package was discontinued). I like the fact that > FreeBSD checks for conflicts early, but erroring out without anything > really useful is a negative for me. Instead of erroring out, why not > initiate some sort of conflict resolution (e.g. remove and or update > an old port) when the conflict is first detected? Yes, it may very > well mean increased time to install a package, especially if > compiling from source, but I find that a more elegant solution then > just erroring out and requiring yet another manual step. Of course > there could be an option to opt-out of this sort of behavior too, for > those who like the extra steps. If I remember correctly, 'portmanager -y' removed conflicting ports prior to installing a new or updated port. -- Jerry gesbbb@yahoo.com |::::======= |::::======= |=========== |=========== | Children begin by loving their parents. After a time they judge them. Rarely, if ever, do they forgive them. Oscar Wilde
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100116145128.32fdd7f0>