Re: [ptp-dev] PTP Juno repository does not contain features that Paralle

[Greg Watson <g.watson@xxxxxxxxxxxx>]

On Mar 22, 2012, at 5:52 PM, Jeffrey Overbey wrote:

In order to build parallel package juno M6 we tried to include these new features
...
But they are not in the common Juno Repository

Just to clarify... it's required that every feature in the EPP package also be in the Juno repository?

Yes, EPP obtains it's features from the Juno repository.

Something feels odd about contributing the jaxb.contrib stuff to the common repo/PTP core... I think because we're filling it with machine-specific RMs, and the Juno repo targets the world.  It would be really nice if the machine-specific RMs (e.g., for Forge, Lonestar, and Blue Waters) would only show up when you connect to that specific machine.

I'm in two minds about this, since it does add a lot of RMs that some people will not use. I think it should probably be kept a separate feature.

We discussed what (not) to do with the cdt.compilers stuff in a previous thread <http://dev.eclipse.org/mhonarc/lists/ptp-dev/msg05736.html>, although merging it into an existing feature is fine with me.  Same with pldt.fortran -- the reasons for separating it are in <https://bugs.eclipse.org/349385>, but merging it into core PLDT is fine with me if you don't mind the Photran dependency.

cdt.compilers should be in ptp.core since it doesn't introduce any dependencies, or clutter the UI particularly.

The fortran features need to be kept separate to avoid a dependency on photran. We now have 3 fortran features (pldt.fortran, etfw.tau.fortran, and sync.fortran), so I think it's worth putting these, along with photran, into a separate fortran feature.

Greg