DaemonForums  

Go Back   DaemonForums > FreeBSD > FreeBSD Ports and Packages

FreeBSD Ports and Packages Installation and upgrading of ports and packages on FreeBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 16th January 2010
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,128
Default FreeBSD ports conflicts handling

From http://lists.freebsd.org/pipermail/f...ry/211053.html:

Quote:
Until recently, it seems like port dependencies were handled at
installation time. Lately, they're handled any time I try to do anything
with a port. I absolutely detest the new behavior. Example cases:

OLD WAY:

$ cd /usr/ports/something/foo22
$ make
$ pkg_delete foo21-2.1
$ make install

NEW WAY

$ cd /usr/ports/something/foo22
$ make
===> foo22 conflicts with installed package(s): foo21-2.1
$ make fetch
===> foo22 conflicts with installed package(s): foo21-2.1
$ curse --type=copious
$ pkg_delete foo21-2.1
$ make install

This isn't just a hypothetical pain in the butt. An example was being
unable to build databases/mysql51-client because
mysql-client-5.0.something was installed. I understand not being able to
*install* it, but to be prevented from *building* it? In most
circumstances, I want to be able to delete the old package and install
the new one with minimal downtime. As another example, can you imagine
not being able to even run "make fetch" on something huge like
OpenOffice until you uninstalled the old version?

In the mean time, I've been editing the port's Makefile to remove the
CONFLICTS line long enough to finish building. That's not very helpful
for those ports that don't actually build until you run "make install",
but at least I can get the distfile download out of the way.
--
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #2   (View Single Post)  
Old 17th January 2010
TerryP's Avatar
TerryP TerryP is offline
Arp Constable
 
Join Date: May 2008
Location: USofA
Posts: 1,547
Default

Who ever changed it, was probably tired of waiting on the compile time lol. A warning instead of a cork popper would be nice for the early targets.
__________________
My Journal

Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Handling ssh login attempts with pf mayuka OpenBSD Security 17 11th January 2010 04:53 PM
libslang2-2.1.4 conflicts with installed package(s): libslang-1.4.9 edhunter FreeBSD Ports and Packages 1 9th October 2008 10:52 AM
Patch and compile bind94 on FreeBSD ports collection dylan912 FreeBSD Ports and Packages 2 4th July 2008 12:23 PM
gnome; librsvg package conflicts bsdnewbie999 OpenBSD General 8 21st June 2008 09:08 AM
FAQ: FreeBSD Ports and Packages Carpetsmoker FreeBSD Ports and Packages 0 1st May 2008 03:38 PM


All times are GMT. The time now is 05:09 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick