Re: Patch for pgAdmin4 RPM package
От | Dave Page |
---|---|
Тема | Re: Patch for pgAdmin4 RPM package |
Дата | |
Msg-id | CA+OCxoxBDt82P75Q4Cy4fBkznkPBW3YJwPz+wFARbBBSoi3fgg@mail.gmail.com обсуждение исходный текст |
Ответ на | Patch for pgAdmin4 RPM package (Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>) |
Ответы |
Re: Patch for pgAdmin4 RPM package
|
Список | pgadmin-hackers |
Hi Team, Dave,Attached herewith are two patches.pgadmin4-rpm.patch - This is the main patch that includes scripts, makefiles and spec to create RPMs for RHEL6/RHEL7/F-22/F-23/F-24.
It will create two RPMs i.e pgadmin4 and pgadmin4-web. The pgadmin4 tpm depends on web and the web rpm depends on the python packages. I have commented the list of packages which are not available on some systems so that Devrim can build them.
The installation path for pgadmin4 is "/usr/pgadmin4-<major>.<minor>" and pgadmin4-web is the site-packages/pgadmin4-web
pgadmin4-server-ini.patch - This is the patch for runtime/Server.cpp. As said pgadmin4-web and runtime installation directories are different and that means web does not exists in parallel to runtime like in sources.
I observed that the location of application settings was not defined in Server.cpp. As per QSettings doc, the default location on Unix is the $HOME/.config/<companyname>/<appname>.conf. Here, $HOME depends on the user that runs the application. So, I thought why not to define the application settings in application directory itself. RPM then knows where to define the ApplicationPath. I tested it and it worked fine with me. I haven't done this change for platform dependent.
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgadmin-hackers по дате отправления: