Replying to Kou's comment: I am not 100% sure -- one way would be to add instructions to
https://github.com/apache/arrow/blob/master/dev/release/VERIFY.md That way at least people can be explicit about what modifications they're making to their system. We could also create a script that creates a standalone directory with Ruby and the requisite system dependencies (GLib, gobject-instrospection), etc., so that you can verify the release without making any system modifications On Wed, Sep 27, 2017 at 8:42 PM, Kouhei Sutou <[email protected]> wrote: > Hi, > > In <CAJPUwMCKfr=w+6xnwi+rbs9ojivdbzh6gdy2okjgxohdtwn...@mail.gmail.com> > "Re: [VOTE] Release Apache Arrow 0.7.1 - RC1" on Wed, 27 Sep 2017 10:12:08 > -0400, > Wes McKinney <[email protected]> wrote: > >> @Kou, we might want to add "cold start" instructions for people who >> want to use the release verification script, and who may not have the >> requisite libraries (Ruby and system C libraries) to build the GLib >> bindings and run the unit tests. > > OK. > Which approach is better? > > 1. Write document for installing requisite libraries on > some platforms such as Debian, Ubuntu, CentOS and macOS > to somewhere such as c_glib/README.md. > 2. Write a script that installs requisite libraries on > some platforms such as Debian, Ubuntu, CentOS and macOS. > > > I'll be able to work on it by 0.8.0. > > > Thanks, > -- > kou
