Opened 9 months ago

Closed 9 months ago

#67970 closed defect (fixed)

unifdef conflicts with developer_cmds

Reported by: barracuda156 Owned by: catap (Kirill A. Korinsky)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: Cc: mascguy (Christopher Nielsen)
Port: unifdef

Description

--->  Activating unifdef @2.12_0
x ./
x ./+COMMENT
x ./+CONTENTS
x ./+DESC
x ./+PORTFILE
x ./+STATE
x ./opt/
x ./opt/local/
x ./opt/local/bin/
x ./opt/local/bin/unifdef
x ./opt/local/bin/unifdefall
x ./opt/local/share/
x ./opt/local/share/man/
x ./opt/local/share/man/man1/
x ./opt/local/share/man/man1/unifdef.1.gz
x ./opt/local/share/man/man1/unifdefall.1.gz
Error: Failed to activate unifdef: Image error: /opt/local/bin/unifdef is being used by the active developer_cmds port.  Please deactivate this port first, or use 'port -f activate unifdef' to force the activation.
    while executing
"throw registry::image-error $msg"
    ("foreach" body line 47)
    invoked from within
"foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to install links, we test if we can lst..."
    invoked from within
"registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be able to instal..."
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_unifdef/unifdef/main.log for details.

Change History (5)

comment:1 Changed 9 months ago by mascguy (Christopher Nielsen)

Cc: mascguy added

comment:2 Changed 9 months ago by mascguy (Christopher Nielsen)

Kirill, is the later version of unifdef backward-compatible, such that it could be added as part of developer_cmds?

Alternatively, could unifdef install binaries with an additional suffix, to allow both ports to co-exist? (With the understanding that any dependent ports will need to look for unifdef/unifdefall, with the additional suffix.)

comment:3 Changed 9 months ago by catap (Kirill A. Korinsky)

Christopher or maybe exclude unifdef / unifdefall from developer_cmds?

comment:4 in reply to:  3 Changed 9 months ago by mascguy (Christopher Nielsen)

Replying to catap:

Christopher or maybe exclude unifdef / unifdefall from developer_cmds?

That's fine too, so long as developer_cmds includes a run dep on unifdef.

comment:5 Changed 9 months ago by catap (Kirill A. Korinsky)

Resolution: fixed
Status: assignedclosed

In ca688085310efafb75a940a1120d39baf43373c7/macports-ports (master):

unifdef: add conflict to developer_cmds

Closes: #67970

Note: See TracTickets for help on using tickets.