New Ticket     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #17452 (closed defect: wontfix)

Opened 3 years ago

Last modified 3 years ago

swig dependencies (was: py25-scipy upgrade goes berserk)

Reported by: ralph@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc: kevin@…, jwa@…, ram@…, mcalhoun@…
Port: swig, py25-scipy

Description

Trying to upgrade py25-scipy on my Mac resulted in swig being required, which in turn proceeded to try to install apache2 ruby php5 all of which are utterly unwanted and utterly inappropriate to my desire to use py25-scipy.

Please reconsider this completely inappropriate behaviour.

Change History

Changed 3 years ago by ram@…

  • cc kevin@…, jwa@…, ram@… added
  • port set to swig, py25-scipy
  • summary changed from py25-scipy upgrade goes berserk to swig dependencies (was: py25-scipy upgrade goes berserk)

As you note this is due to the dependencies of swig, specifically due to the fact of having the perl, python, ruby, and php5 variants turned on by default. To get round this I install swig by hand with only the variants I'm interested in i.e.:

$ sudo port install swig -ruby -php5

before installing py25-scipy.

Can the number of these default variants be toned down?

Changed 3 years ago by jmr@…

This is basically the classic use case for #126. Install swig without the right bindings and its dependents break, but nobody actually wants all the bindings.

Changed 3 years ago by ralph@…

Doing the following

sudo port -f uninstall swig
sudo port install swig -ruby -php5

says

Installing swig 1.3.36_1+perl+python

Then doing

sudo port upgrade installed 

still results in attempts to install ruby, apache2, php5 and so on. This "workaround" does not fix the problem. Please note ruby, apache2, php5 etc were *not* installed before.

Changed 3 years ago by jmr@…

That's because of #2377.

Changed 3 years ago by mcalhoun@…

  • cc mcalhoun@… added

Cc Me!

Changed 3 years ago by mcalhoun@…

Since no improvement can be made without a fix to either #126 or #2377, can this ticket be closed?

Changed 3 years ago by ralph@…

I suppose so, but please add a cross reference to those tickets if there is not one already.

Changed 3 years ago by mcalhoun@…

  • status changed from new to closed
  • resolution set to wontfix

Cross-references to #126 and #2377 added.
We can revisit the issue when either one is fixed.

Changed 3 years ago by anonymous

  • milestone Port Bugs deleted

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.