[MacPorts] #32716: geant4: update to 9.5

[MacPorts]

#32716: geant4: update to 9.5
---------------------------+---------------------------------
  Reporter:  ryandesign@…  |      Owner:  cristiano.fontana@…
      Type:  update        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:                |   Keywords:
      Port:  geant4        |
---------------------------+---------------------------------

Comment (by macsforever2000@…):

 Replying to [comment:17 mojca@…]:
 > > > - '''Smooth transition from 4.9.4''': I'm not sure what is needed or
 how to implement it.
 > >
 > > Make the current {{{geant4}}} port {{{replaced_by geant4.9.6}}}.
 > If I understand correctly this is only possible if the new port is
 called {{{geant}}}?

 I believe so but someone please correct me if I'm wrong.

 > > > - Decide on exact subport name: {{{geant4.9.6}}}?
 > >
 > > I like the this. The perl ports (messed up as the perl situation is)
 are a good example. I never liked the python/ruby model which omits the
 periods. The ruby186 port is a good example of a confusing name.
 >
 > But then I have another question for you: how would you name the patch
 files (I currently have {{{patch-cmake-Modules-
 Geant4BuildProjectConfig.cmake.4100.diff}}} for example) and variants
 ({{{gate}}} could depend on two different versions of geant, I called them
 {{{geant495}}} and {{{geant496}}}; would more verbose variant names be
 better?)

 I wouldn't worry about renaming patches. Those are for port maintainers
 only. As for variants, I'm not actually sure if having a period in a
 variant name is valid. I can't think of a variant name that uses one so
 probably best to stick to {{{geant495}}} etc.

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