[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] Building PTP features for Fedora package
|
Currently in releng/org.eclipse.ptp.master/feature.xml there is:
$ grep -F id= feature.xml
id="org.eclipse.ptp.master"
id="org.eclipse.rephraserengine"
id="org.eclipse.photran"
id="org.eclipse.photran.intel"
id="org.eclipse.photran.xlf"
id="org.eclipse.ptp.core"
id="org.eclipse.ptp.pldt.upc"
id="org.eclipse.ptp.rdt"
id="org.eclipse.ptp.remote.rse"
id="org.eclipse.ptp.etfw.tau"
id="org.eclipse.ptp.etfw.tau.fortran"
id="org.eclipse.ptp"
id="org.eclipse.ptp.rdt.xlc"
id="org.eclipse.ptp.rdt.remotetools"
id="org.eclipse.ptp.rdt.remotejars"
id="org.eclipse.ptp.sci"
id="org.eclipse.ptp.gem"
id="org.eclipse.ptp.etfw.ppw"
Previously (3.0.X days) there was:
id="org.eclipse.ptp.master"
id="org.eclipse.ptp.utils"
id="org.eclipse.ptp.services"
id="org.eclipse.ptp.remote"
id="org.eclipse.ptp.core"
id="org.eclipse.ptp.external"
id="org.eclipse.ptp.debug.sdm"
id="org.eclipse.ptp.pldt"
id="org.eclipse.ptp.pldt.lapi"
id="org.eclipse.ptp.pldt.upc"
id="org.eclipse.ptp.rdt"
id="org.eclipse.ptp.remotetools"
id="org.eclipse.ptp.remote.remotetools"
id="org.eclipse.ptp.remote.rse"
id="org.eclipse.ptp.rm.ibm.ll"
id="org.eclipse.ptp.rm.ibm.pe"
id="org.eclipse.ptp.rm.mpich2"
id="org.eclipse.ptp.rm.openmpi"
id="org.eclipse.ptp.etfw"
id="org.eclipse.ptp.etfw.tau"
id="org.eclipse.ptp.etfw.tau.fortran"
id="org.eclipse.ptp"
id="org.eclipse.ptp.rm.slurm"
id="org.eclipse.ptp.rm.pbs"
id="org.eclipse.ptp.isp"
id="org.eclipse.ptp.rdt.xlc"
id="org.eclipse.rephraserengine"
id="org.eclipse.photran"
id="org.eclipse.photran.intel"
id="org.eclipse.photran.xlf"
Many were removed here:
Revision 1.45 - (view) (download) (as text) (annotate) - [select for diffs]
Thu May 20 18:47:09 2010 UTC (3 months, 1 week ago) by gwatson
Branch: MAIN
CVS Tags: v201005201458, v201005201841, v201005202008, v201005202228
Changes since 1.44: +1 -65 lines
Diff to previous 1.44
Added SCI. Removed duplicate features.
My goal is the build the features independently so that they can be installed
independently instead of in one big chunk. If there is a better way to
achieve that, let me know.
On 08/30/2010 01:59 PM, Greg Watson wrote:
Orion,
The master feature still contains all the features for ptp, they are just grouped a bit differently than in 3.0, so I'm not quite sure I understand your problem.
Regards,
Greg
On Aug 26, 2010, at 12:24 AM, Orion Poplawski wrote:
I'm back :-)
So, back when I was trying to package PTP 3.0.X for Fedora, ptp.master/feature.xml appeared to have contained all of the component features of PTP. I assumed that this is what was used to build the whole shebang.
For Fedora, however, I believe it would be desirable to be able to install only the particular components that a user wants. So, I built the features individually using the master feature.xml as the source for the list and for the build order.
Now with 4.0.2, it appears that only a few features are listed in master feature.xml. I imagine that however your release builds are done that dependency ordering is not automatically determined?
I'm now left with trying to figure out how to determine what features to build and in what order. Any help would be appreciated.
Thanks!
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxxxxxxx
Boulder, CO 80301 http://www.cora.nwra.com
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxxxxxxx
Boulder, CO 80301 http://www.cora.nwra.com
