alinaliBQ commented on issue #55383: URL: https://github.com/apache/arrow/issues/55383#issuecomment-6670055381
@raulcd @amoeba Tl;dr, After some consideration, I am now leaning towards updating documentation instead of adding a new CI for this GH issue, because `Package Linux` already builds the ODBC RPM installers. Currently I don't have capacity to do the documentation, but I might be able to some time later. - - - - - - - - > The user triggers a workflow dispatch event for a specific distro on their fork to generate the specific installer? Yes > Will this be run on nightlies too? No. Good point raised on lack of notification about failed workflows, I think that is the downside of making it dispatch-only. > How complex is to maintain the different distros vs documenting to devs how to build this themselves? Now that you mention it, I think documenting to devs might be easier. 1) Instructions to specify package to build is not documented in `linux-packages/README.md`, and I am also not sure if the current implementation supports that. If this is supported, then I think it is a reasonable doc gap to cover. 2) There is currently one path to get ODBC RPM from CI: By running `Package Linux` job and extracting ODBC-libs RPM from the generated tarball for desired target distro. Would documenting this be helpful? Or would it create more maintenance burden in case `Package Linux` gets updated? > do we have a documented need for this or is this just theoretical? Just theoretical. I am going on a tangent here, and I think other developers might run into the same thing with non-ODBC Linux installers. Currently `Package Linux` builds all supported installers on all distros, and if there is an option to specify which packages/distros to build, it would help reduce CI time, but it should be a separate GH issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
