Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP 7.4 fixes #22

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

PHP 7.4 fixes #22

wants to merge 3 commits into from

Conversation

ramereth
Copy link
Contributor

  • Set workdir as a library so this works on EL8
  • PHP 7.4 fixes
  • Move phpCAS module to composer

ramereth added 3 commits June 7, 2024 08:57
- Create composer.json and migrate to using smarty 5.3
- Switch to autoloadingn from composer
- Various updates to get support for PHP 7.4

Signed-off-by: Lance Albertson <[email protected]>
Signed-off-by: Lance Albertson <[email protected]>
@ramereth ramereth marked this pull request as ready for review June 12, 2024 18:04
@tillkamppeter
Copy link
Member

I have one question here:

Most of the code contained in this repo, especially after your PHP 7.4 migration seem to be copies of third-party libraries (I assume that you did not write ~70000 lines of code in such a short time). Is it really required to carry them in our repo? Can one not just mention them as dependencies in the documentation and tell the user to install them in order to use our code?

There are several disadvantages of such code copies:

  • The repo gets huge
  • If the added library has a new upstream release we would have to replace it in our code
  • Even worse if the upstream library has a security bug

And even more a maintenance nightmare it gets if you did small changes in the copied library code ...

@ramereth
Copy link
Contributor Author

@tillkamppeter the additional code I added is the output of the composer install so it's vendored libraries. We could in theory move this out of the repository and just keep the composer.json/lock files if you prefer and then do the composer install via our configuration management system on the system itself. Let me know how you'd like to proceed.

@ramereth
Copy link
Contributor Author

ramereth commented Jul 9, 2024

@tillkamppeter can we please get this merged soon?

@tillkamppeter
Copy link
Member

@tillkamppeter the additional code I added is the output of the composer install so it's vendored libraries. We could in theory move this out of the repository and just keep the composer.json/lock files if you prefer and then do the composer install via our configuration management system on the system itself. Let me know how you'd like to proceed.

What are "vendored libraries"? Is it not possible to make foomatic-db-webapp installable on arbitrary servers with a lower amount of copied (and perhaps slightly modified, where it is not clear what got modified) code which this way gets maintained independently at two places (here and at the original place)?

Would be the "just keep the composer.json/lock files" way then not be the better way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants