[Evergreen-general] libdbi PostgreSQL driver not found in shared library path

[Dashamir Hoxha]

On Sun, Nov 3, 2024 at 8:58 PM Dashamir Hoxha <dashohoxha at gmail.com> wrote:

>
> Let us know if you encounter a specific error, and maybe we can
>> troubleshoot that. I hope you get it setup and working! We're a fun
>> community of developers and librarians alike, and your suggestions and
>> improvements are very much welcome!
>>
>
> I carefully followed all the steps on the installation page, but it didn't
> work. Maybe it is only something very small that needs to be fixed, but I
> cannot figure it out because I am not familiar with all this stuff. If
> someone could spend 15-20 minutes debugging it, just to check for anything
> unusual, this might be a great help.
> I am willing to have a short online meeting, whenever it is suitable for
> you.
>

I had a very useful/productive meeting with Blake yesterday, and he helped
me to fix a couple of issues that would have been difficult for me to find
out on my own. Now that I have an installation that works, I can work to
improve it and make it better.

> your suggestions and improvements are very much welcome!

I can make a few humble suggestions on how to improve the project, based on
my experience and what I have seen on other projects.

- Maybe you are used to GitWeb, but my impression is that most of the
people are familiar with GiLab or GitHub. GitLab can also be installed on
your own server (although I have never tried it). I would suggest migrating
from GitWeb to GitLab.

- Instead of supporting several Debian/Ubuntu versions, it might be better
to support only one of them (for example the latest Debian stable). If I
want to install EG, I would pick the latest version of Debian, and I would
install it on a fresh installation (nothing else installed on it). For
people who have installed it on previous Debian versions, they need an
upgrade path (instructions) to the latest version.

- The same for PostgreSQL, no need to support all the versions for
different systems. It doesn't make much sense to me.

- I would prefer that the installation instructions for production and
development are on separate pages, even if they have some (or many) common
steps. On the other hand, the installation steps of OpenSRF should be
included on the installation page of EG, even if they are described on the
OpenSRF page.

- I don't have much knowledge about "make" and Makefile, but my opinion is
that it is not the appropriate tool for installing dependencies. You can
use DEB packages instead, which might be more suitable. Or just bash
scripting, or listing the packages that need to be installed on the
installation page.

- When I subscribed to the mailing list, the confirmation message somehow
ended up in the Spam folder. I was lucky to find it, other people may have
missed it. Maybe there is something to be fixed here.

- I would suggest migrating from Mailman to Discourse, which is much better
(in my opinion). Installing and maintaining it is not too difficult.
Migrating from mailman is not difficult either. I have done it a few times
in the past, I have also written some notes:
https://docker-scripts.gitlab.io/apps/discourse.html#_import_mailman3_archives
If you decide to do it you may count on my help.

Regards,
Dashamir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20241105/780b3b2e/attachment.htm>