Scott,
You run a great site and repository. Thank you for all your hard work.
From what I understand of PSA incompatibilities with some software it seems backwards to patch things likes SA, PHP, MySQL etc. Isn't it really PSA that is incompatible, and should be patched? This may not be possible of course, but just wondering the reasons behind it. Either way you have saved a lot of servers and a lot of headaches for us.
-Dave
PSA/Plesk patches instead?
-
scott
- Atomicorp Staff - Site Admin
- Posts: 8355
- Joined: Wed Dec 31, 1969 8:00 pm
- Location: earth
- Contact:
Good point, maybe I should just stop making rpms then! 
Seriously though, no I rarely have to modify things to be compatible with PSA, its more along the lines of putting things out that are useful in a web hosting environment. For the most part all the packages in my archive run equally well in a non-PSA system. In the cases where there are PSA specific changes, they are generally related to configuration files. Clam AV for example, needs to run as the user qmailq, so I use triggers inside the rpm to run as qmailq, only if psa is detected.
This is entirely the reason that I was so adament about using RPM's rather than rolling our own daemons back at Plesk.
Seriously though, no I rarely have to modify things to be compatible with PSA, its more along the lines of putting things out that are useful in a web hosting environment. For the most part all the packages in my archive run equally well in a non-PSA system. In the cases where there are PSA specific changes, they are generally related to configuration files. Clam AV for example, needs to run as the user qmailq, so I use triggers inside the rpm to run as qmailq, only if psa is detected.
This is entirely the reason that I was so adament about using RPM's rather than rolling our own daemons back at Plesk.