Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#25175 closed defect (fixed)

protobuf-python, protobuf-python25, protobuf-python26: noarch

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: blair (Blair Zajac)
Priority: Normal Milestone:
Component: ports Version: 1.8.99
Keywords: Cc:
Port: protobuf-python, protobuf-python25, protobuf-python26

Description

protobuf-python, protobuf-python25, protobuf-python26 should be marked as noarch, which will also (now that MacPorts 1.9.0 is out) fix the problem that protobuf-python26 has a universal variant.

Change History (8)

comment:1 Changed 14 years ago by blair (Blair Zajac)

Do I need to bump the revision?

comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Probably not necessary.

comment:3 Changed 14 years ago by blair (Blair Zajac)

Status: newassigned

I see the autoconf Port has this:

if {[info exists supported_archs]} {
    supported_archs noarch
} else {
    universal_variant no
}

Do I need all of this or just the "supported_archs noarch" now that MacPorts 1.9.0 is out?

comment:4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Only "supported_archs noarch" is needed with 1.9.0. But we might wait a couple weeks before removing the workarounds from ports, to give people time to upgrade to 1.9.0.

comment:5 Changed 14 years ago by blair (Blair Zajac)

So you're suggesting for now to use the syntax that autoconf uses?

comment:6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Yes, it might prevent a few tickets from being filed by users who haven't realized 1.9.0 is available yet. In a couple weeks we can make a sweep through all ports to remove these bits.

comment:7 Changed 14 years ago by blair (Blair Zajac)

Resolution: fixed
Status: assignedclosed

Thanks, fixed in r68666.

BTW, supported_archs isn't documented in man portfile. Should I open a ticket?

comment:8 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

There are a great many things missing and outdated in the portfile manpage, it seems, but yes, please file a ticket.

Note: See TracTickets for help on using tickets.