Phil:
If we need to get legal involved (and I am not suggesting it until you feel it is appropriate), I have the connections to get that moving. Just let me know. From: [email protected] [mailto:[email protected]] On Behalf Of Phillip Moore Sent: Monday, December 13, 2010 8:38 AM To: EFS core development list Subject: [EFS-dev] Java meets EFS 3 At the request of the ServiceMesh folks, I've started working on integrating the core Java infrastructure with EFS 3, and this creates some interesting new problems. First of all, I've been able to cleanly integrate the Oracle/Sun JRK/JRE releases, which are very straight forward (basically just unpack the distribution into the install tree). These can be downloaded form openefs.org, by creating the "java" metaproj, and setting it up for download in the same way as all the other metaprojs, and then running: efs download release java sunjdk 6u23 efs download release java sunjre 6u23 Here I followed the metaproj/project convention we used in EFS 2, although you could certainly argue that we should be maintaining the Oracle/Sun binary only releases in the oracle metaproj. Table that for now.... The above integration required patching efsdeploy to support shell archives, and build-specific macro expansion of the archive file pathname I was about to start working on the IBM JDK/JRE, but these packages have a particularly annoying dependency: compat-libstdc++. IBM's binaries depend on the gcc 3.2.3 libstdc++, which is not part of the default RHEL5 builds. Now, this is a problem, because I think we're playing with fire by redistributing binaries from these vendors, which is why we need to have a discussion about this. First of all, you can't even download the Oracle/Sun *or* IBM Java distributions without clicking your way through some licensing legalese. This makes me particularly nervous about repackaging and redistributing these binaries. The same is then true for the RHEL 5 binary rpms. You need a RedHat login to get the official binaries, although we *could* workaround this by simply building gnu/gcc/3.2.3 (and/or rhel/gcc/3.2.2) and providing a natively compiled libstdc++ that can be used to satisfy the requirements of the IBM Java products. However, if we are going to package these products and share them via openefs.org, I think we're asking for legal trouble, since we're effectively redistributing these products, just packaged in a different way. We certainly don't ask anyone to click through Oracle or IBM's license pages. Before I go any further with the IBM Java products, I think we need to have a discussion about the legal issue, since this is the first time we've packaged something we did not compile from source code ourselves. I have already completed the Oracle/Sun integration, and I'll go ahead and package up some of the open source java products, but some of the other Java infrastructure has similar issues. For example, JBoss -- can't download that without a RedHat login, either, so while it's "open", it's not exactly trivial to acquire. Opinions? Feedback? ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
