[
https://issues.apache.org/jira/browse/MADLIB-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841258#comment-17841258
]
David E. Wheeler commented on MADLIB-1518:
------------------------------------------
I see [far more files|[https://api.pgxn.org/src/madlib/madlib-2.1.0/]] now,
yes, including {{{}configure{}}}. From the
[README[[https://api.pgxn.org/src/madlib/madlib-2.1.0/ReadMe_Build.txt]] it
looks like one would need to {{cd}} into the {{build}} directory before running
{{{}make{}}}. This is a different pattern from most automate-generated
projects, though, where one runs {{make}} in the same directory. This will make
it difficult for something like the [pgxn
client|https://pgxn.github.io/pgxnclient/] to to automate installation, as it
would need to special-case the pattern for madlib. Would it be possible to
remove the need to {{cd}} into the {{build}} directory?
> Files missing from PGXN Release
> -------------------------------
>
> Key: MADLIB-1518
> URL: https://issues.apache.org/jira/browse/MADLIB-1518
> Project: Apache MADlib
> Issue Type: Bug
> Reporter: David E. Wheeler
> Assignee: Ed Espino
> Priority: Major
> Attachments: MADlib-setup.out
>
>
> Starting with the 1.19.0 release, the PGXN distribution is missing most of
> its files. Compare:
> * [v1.18.0|https://api.pgxn.org/src/madlib/madlib-1.18.0/]
> * [v1.19.0|https://api.pgxn.org/src/madlib/madlib-1.19.0/]
> * [v1.20.0|https://api.pgxn.org/src/madlib/madlib-1.20.0/]
> This means users can no longer use the PGXN client to build and install
> madlib. Was this intentional?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
