[
https://issues.apache.org/jira/browse/PARQUET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086427#comment-15086427
]
Wes McKinney commented on PARQUET-267:
--------------------------------------
Per discussion on PARQUET-416; I'll split out the code reorganization into its
own patch so we can figure out a plan here. I'm happy using
https://github.com/apache/parquet-cpp/pull/10 as a starting point and adding
`${LIBNAME_HOME}` variables so that one can easily set up a custom toolchain
with environment variables.
> Relax Third Party Dependency Restrictions
> -----------------------------------------
>
> Key: PARQUET-267
> URL: https://issues.apache.org/jira/browse/PARQUET-267
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-cpp
> Reporter: Kalon Mills
> Priority: Minor
>
> The existing repo has source code for third party dependencies checked into
> the repo. The build system expects those dependencies in a certain place.
> This enforces that the built library conform to those exact dependencies
> without customization.
> Managing third party dependencies is better handled through a build
> environment. It allows the library builder more flexibility over dependency
> versions and locations. It also cleans up the repo from this third party
> code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
