a quick question: I am just trying to update neos.io to dev-master (for testing purposes); and doing that I figured out that many 3d party packages (e.g. https://github.com/ttreeagency/OutOfBandRendering https://github.com/jonnitto/Jonnitto.PhotoSwipe or https://github.com/punktDe/PunktDe.CodeView) use dependencies to Neos like:
"neos/neos": "^3.0 || ^4.0"
-> Thus, the package is not installable on dev-master.
How to proceed here?
- every external package should be patched to include
- another option I don’t understand yet?
All the best,
What about installing Neos and Flow as:
"neos/neos-development-collection": "dev-master as 4.3.0",
"neos/flow-development-collection": "dev-master as 5.3.0",
true, that would be an option – though then packages which explicitely target
dev-master would not be installable. So either we recommend against using
dev-master - or we find a different way
BTW - I don’t fully get the difference between
dev-master yet… Seems I have a lot to learn about composer
All the best,
PS: I am having above problems from time to time; maybe it’s time to find a best practice there (or if it exists, document it somewhere )
What @daniellienert suggested is the way to go. Packages that explicitly require dev-master are, well… suspicious. And rarely seen.
The difference between
- @dev` is a stability flag, saying “it’s ok to use a dev version of that package” - in whatever version, so it could be any branch. And it might resolve to a stable (or alpha, beta, rc) version instead.
dev-master says: “install the tip of the master branch”.