Skip to content

Conversation

@a4blue
Copy link

@a4blue a4blue commented Dec 1, 2021

No description provided.

Copy link
Collaborator

@Ocramius Ocramius left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Source-wise, this is fine, but in practice I would rather get rid of symfony/* as a dependency, perhaps including the upstream sources and relevant tests, rather than introducing a dependency.

"require": {
"php": "^7.3 || ^8.0.0",
"webmozart/path-util": "^2.2"
"symfony/filesystem": "^5.4"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit vary on introducing symfony/* dependencies, since they are inherently unsafe from a dependency PoV:

https://github.com/symfony/filesystem/blob/731f917dc31edcffec2c6a777f3698c33bea8f01/composer.json#L19

See also #57

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since there is at least one other Project that does not want to use the symfony Project for the same reasons, i tried to Fork it and update it in this Project https://github.com/a4blue/path-util
If i require it instead, i think it should be ok with everyone :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Ocramius What's the stance of the Symfony team on that?

Copy link
Collaborator

@Ocramius Ocramius Dec 9, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No idea: tbh, including their classes (renamed, with a licence notice here) is probably the safest bet.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right now merging and releasing this is still better than keeping the abandoned repo in there as dependency.
Along the lines quite a few libraries now generate the warning report here:

Package webmozart/path-util is abandoned, you should avoid using it. Use symfony/filesystem instead.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But in that case a higher support for also Symf 4/5/6 might be good.

Or indeed the classes are just copied - as long as you keep the original copyright (license header), it will be fine.
Thats even easier and will have less dependency issues with symfony and changing their signature/code.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right now merging and releasing this is still better than keeping the abandoned repo in there as dependency.

Not really a problem until a security issue occurs.

I suggest sending a patch with the necessary upstream dependency code, license headers and tests included.

@Ocramius
Copy link
Collaborator

Ocramius commented Apr 5, 2022

Removed dependency in #60

@Ocramius Ocramius closed this in #60 Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants