Bug 61985

Summary: A suggestion for CONFLICTS in ports
Product: Ports & Packages Reporter: Michael Johnson <ahze>
Component: Individual Port(s)Assignee: Port Management Team <portmgr>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Michael Johnson 2004-01-27 10:20:13 UTC 
The CONFLICTS feature in ports is a nice feature but I feel it is lacking a simple but useful feature. I know about DISABLE_CONFLICTS, but I feel it would be nice to also be able to do something like, OVERRIDE_CONFLICTS="thttpd-2.* apache-2.*", and this would allow apache2 and thttpd, to be installed on the same box with out ports telling me they conflict. 

I looked at bsd.port.mk and I wasn't quite sure where to begin so I am just sending this as a simple suggestion. 

Thanks, 
  Michael Johnson
Comment 1 Pav Lucistnik freebsd_committer freebsd_triage 2004-01-27 11:55:52 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->portmgr

Over to portmgr to consider
Comment 2 Sergey Matveychuk 2004-01-30 00:24:44 UTC 
Why?

Conflicted ports have files placed in the place.
So if you install two conflicted ports, a second one overwrites file(s) 
from a first one. So you'll brake the first port. There is no guarantee 
this port will work with files from the second ports. Anyway it will 
lose these files when you'll deinstall the second port.

A better solituion is to install conflicted ports with a defferent PREFIXes.

---
Sem.
Comment 3 Michael Johnson 2004-01-30 03:35:00 UTC 
The example I gave with thttpd and apache2 install nothing in the same 
place. The only reason I see why they CONFLICT is because they both use 
port 80 as the default port.
There is many other ports like the example I gave, and it would be nice 
to have some variable  that have to be defined, for example 
OVERRIDE_CONFLICTS="apache2 thttpd-" would only allow apache and thttpd 
be installed with out printing the conflict error.

Michael

On Jan 29, 2004, at 7:24 PM, Sergey Matveychuk wrote:

> Why?
>
> Conflicted ports have files placed in the place.
> So if you install two conflicted ports, a second one overwrites 
> file(s) from a first one. So you'll brake the first port. There is no 
> guarantee this port will work with files from the second ports. Anyway 
> it will lose these files when you'll deinstall the second port.
>
> A better solituion is to install conflicted ports with a defferent 
> PREFIXes.
>
> ---
> Sem.
>
Comment 4 Sergey Matveychuk 2004-01-30 09:37:21 UTC 
Mike Johnson wrote:
> The example I gave with thttpd and apache2 install nothing in the same 
> place. The only reason I see why they CONFLICT is because they both use 
> port 80 as the default port.

I think it's stupid to use CONFLICTS this way. The idea CONFLICTS was 
for conflicts files.

---
Sem.
Comment 5 Michael Johnson 2004-01-30 09:41:35 UTC 
I know, That is why I emailed the mailing list.
Michael

On Jan 30, 2004, at 4:37 AM, Sergey Matveychuk wrote:

> Mike Johnson wrote:
>> The example I gave with thttpd and apache2 install nothing in the 
>> same place. The only reason I see why they CONFLICT is because they 
>> both use port 80 as the default port.
>
> I think it's stupid to use CONFLICTS this way. The idea CONFLICTS was 
> for conflicts files.
>
> ---
> Sem.
>
Comment 6 Kris Kennaway freebsd_committer freebsd_triage 2004-03-21 02:57:02 UTC 
State Changed
From-To: open->closed

CONFLICTS isn't used in this way.