kou commented on issue #55435:
URL: https://github.com/apache/arrow/issues/55435#issuecomment-6713976209

   > 1.
   
   Hmm... I think that it's difficult and useless...
   
   In general, `.rpm`/`.deb` packages always use the same build options. We can 
change them dynamically by `%if`/`if`:
   
   
https://github.com/apache/arrow/blob/1ebb9379b2f635755e773b79e88cb99852c70455/dev/tasks/linux-packages/apache-arrow/yum/arrow.spec.in#L154-L156
   
   
https://github.com/apache/arrow/blob/1ebb9379b2f635755e773b79e88cb99852c70455/dev/tasks/linux-packages/apache-arrow/debian/rules#L23-L27
   
   It introduces some complexities. So I want to avoid it as much as possible.
   
   If we change some build options for each CI job, we'll get different 
packages from some CI jobs. But our official `.rpm`/`.deb` packages always use 
the same build options. So building/testing different options aren't affected 
to our official packages. If we think "it's OK" for packages built with 
different options but it doesn't mean that "it's OK" for packages built with 
the build options for our official packages. So I think that we should 
build/test with the official options not different options.
   
   > 2.
   
   Hmm... I think that it's not so useful. Our `.rpm`/`.deb` package 
configurations are shared with multiple distributions. So we should check all 
distributions.
   
   We need to add the `CI: Extra: Package: Linux` label explicitly to run 
packaging jobs. So reduced CI time by this idea will be limited.


-- 
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]

Reply via email to