A few questions about SciFortran and it's packaging

[band-a-prend]

On trying linux packaging of SciFortran a few questions can be interesting to maintainers (+ user repos). I'm trying to summurize some of them.

• Third-party libraries (arpack, fftpack, minipack, quadpack): are modified versions of them are used (except cmake-files)? Is it possible to unbundle it and use upstream system installed package? Is arpack-ng (instead of arpack) is used really?

• Names and directories structure convention: as I could see the installation directory structure currently aimed to install into user (non-system) environment, isn't? The current CMakeLists.txt and additional .sh scripts look to be aimed for this purpose.
  As example the recommended path where pkg-config searches packages .pc files is /usr/lib/pkgconfig/ or /usr/share/pkgconfig/ and library path /usr/lib/ (the /usr/lib64/ paths could be used instead of /usr/lib/ in some distributives of amd64/x86_64 arch - but it's easy to patch in place on packaging). Modules could be placed into /usr/include/scifor. Under actively enchancement process of CMakeLists.txt it's easily currently in my case (for gentoo) to skip cmake install phase and force to direct installation of .so library, .pc file and modules to approriate ststem directories.

• Release circle: could it be less often, with accumulation of several fixes and features? Many places of scifor project store version number and it's frozen at 4.7.3 - it will be easier to change it once on separate "release commit" etc.

• Documentation, examples, tests: the documentation writing is very time-consuming process. The examples are easier to create (but still require time) and could be used for tests later. The support of scifor users with examples could be helpful and is welcome :)
  The examples could be even made on the base of scipy documentation. The good starting point is creation of structured list of implemented procedures and functions.