[MacPorts] #24233: advancemame and advancemenu conflict
MacPorts
noreply at macports.org
Fri Mar 26 15:38:04 PDT 2010
#24233: advancemame and advancemenu conflict
-------------------------------------+--------------------------------------
Reporter: ryandesign@… | Owner: milosh@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: advancemame, advancemenu
-------------------------------------+--------------------------------------
advancemame and advancemenu conflict:
{{{
$ sudo port install advancemame
---> Computing dependencies for advancemame
---> Fetching advancemame
---> Verifying checksum(s) for advancemame
---> Extracting advancemame
---> Applying patches to advancemame
---> Configuring advancemame
---> Building advancemame
---> Staging advancemame into destroot
---> Installing advancemame @0.106.1_0+darwin_i386+universal
---> Activating advancemame @0.106.1_0+darwin_i386+universal
Error: Target org.macports.activate returned: Image error:
/opt/local/share/doc/advance/advcfg.html is being used by the active
advancemenu port. Please deactivate this port first, or use 'port -f
activate advancemame' to force the activation.
Error: Status 1 encountered during processing.
}}}
Is this intentional? I thought advancemame and advancemenu were meant to
work together. But if the conflict is intentional, both ports should be
marked as conflicting with one another using the "conflicts" keyword.
--
Ticket URL: <http://trac.macports.org/ticket/24233>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list