Opened 10 years ago

Closed 10 years ago

#45894 closed enhancement (fixed)

py27-nibabel @1.3.0_1 py-nibabel has unnecessary dependency to gcc (4.7 by default)

Reported by: ghweber@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.2
Keywords: haspatch Cc: seanfarley (Sean Farley), petrrr
Port: py-nibabel

Description

To my knowledge (installing nibabel outside MacPorts and browsing the git repository), this port is pure Python and does not compile any C/C++ source. After removing all gcc related variants, this port still installs fine on my MacOS 10.10 machine and no longer pulls in gcc 4.7 as a dependency.

Attachments (1)

py-nibabel-Portfile.patch (1.4 KB) - added by ghweber@… 10 years ago.

Download all attachments as: .zip

Change History (6)

Changed 10 years ago by ghweber@…

Attachment: py-nibabel-Portfile.patch added

comment:1 Changed 10 years ago by ghweber@…

How can I add "haspatch" to the keywords? I forgot when I created the ticket.

comment:2 Changed 10 years ago by larryv (Lawrence Velázquez)

Keywords: haspatch added
Port: py-nibabel added

comment:3 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: sean@… added

These variants have been there since the port was added in r104370. Sean, do you remember why these variants were added, or were they copied by mistake? Looks like py-nibabel was copied from py-pynifti, which has had those variants since it was added in r104367. py-pynifti was copied from py26-pynifti, which has had gcc variants since r68906, before which it forced the use of gcc43, which had been there since py26-pynifti was added in r56252. The gcc43 requirement was first added to the py25-pynifti port in r53084; the commit message does not say why.

Last edited 10 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:4 Changed 10 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:5 Changed 10 years ago by petrrr

Resolution: fixed
Status: newclosed

The gcc variants were removed with the update in r130956, so this ticket is fixed.

Note: See TracTickets for help on using tickets.