[
https://issues.apache.org/jira/browse/HAWQ-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183793#comment-15183793
]
xin zhang commented on HAWQ-490:
--------------------------------
+1. There has to be a standard way to figure out dependencies, and some best
practice in the OSS community.
At this moment, I see following building blocks:
. Add tag marking for the release of dependent repos, e.g., GPORCA, GPOS, and
GPXERCES in our case.
. Figure out OSS best practice of version dependency in package manager
(https://en.wikipedia.org/wiki/Package_manager). At least we need a popular
Linux flavor (apt-get) and an OSX one (brew) for deployment and development.
. Automate the testing (e.g. Travis) with dependencies using those package
managers.
> Add version and compatibility detection for HAWQ + GPORCA
> ---------------------------------------------------------
>
> Key: HAWQ-490
> URL: https://issues.apache.org/jira/browse/HAWQ-490
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Build
> Reporter: Jacob Max Frank
> Assignee: Lei Chang
> Priority: Minor
>
> Autoconf should be able to detect GPORCA version information and check for
> compatibility with the version of HAWQ being built. Additionally, running
> {{select gp_opt_version();}} on HAWQ compiled with GPORCA should output
> correct version information for its components (GPOPT, GPOS, and GPXerces).
> [~rvs] suggested using {{pkgutil}}. Alternate potential strategies include
> using a {{git submodule}} or pulling values from a {{version.h}} file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
