[MacPorts] #40249: py-obspy @0.8.4_0: update compiler variants

[MacPorts]

#40249: py-obspy @0.8.4_0: update compiler variants
------------------------------+--------------------------------
  Reporter:  Peter.Danecek@…  |      Owner:  macports-tickets@…
      Type:  enhancement      |     Status:  new
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:
Resolution:                   |   Keywords:  haspatch
      Port:  py-obspy         |
------------------------------+--------------------------------

Comment (by Peter.Danecek@…):

 Replying to [comment:1 larryv@…]:
 > Replying to [ticket:40249 Peter.Danecek@…]:
 > > **Some doubt:**
 > > Before the variants were available only for the
 > > subports. It was inside the `if {${subport} != ${name}}` block.
 > > However, it probably would make sense to have variants for the
 > > "superport" as well. This would than pass the variant to the default
 > > subport. Now, this constrain probably is present.
 > >
 > > So how would this be implemented correctly?
 >
 > I don’t see why this should be necessary. MacPorts base already passes
 variant selections to dependencies.

 Well I ended up with something like this:
 {{{
 [radegast:ports/python/py-obspy] petr% port installed | grep obspy
   py-obspy @0.8.4_1+gcc48 (active)
   py26-obspy @0.8.4_1+gcc47 (active)
   py27-obspy @0.8.4_1+gcc45 (active)
 }}}

 So I assumed, it would not work.
 From documentation I concluded it would not be even possible to depend on
 specific variants, so I was thinking to revert to the previous behaviour.

-- 
Ticket URL: <https://trac.macports.org/ticket/40249#comment:2>
MacPorts <http://www.macports.org/>
Ports system for OS X