Easiest way to use a cloned more recent Neos Package from github?

Using Neos & Flow
1

Hey,
there are packages, they still doesn’t support Neos 3.0 in the official Packagist-Version. But there are working solution (with Pull-Requests) – waiting for review and combine on Github.

Is there some easy way to use the 3.0 updated version like jonnitto’s MoveAlong under «https://github.com/jonnitto/Sitegeist.MoveAlong/blob/master/composer.json»

tried with composer.json

"repositories": [        
        {
            "type": "git",
            "url": "https://github.com/jonnitto/Sitegeist.MoveAlong.git"
        }
    ],
    "require": {
        "neos/neos": "~3.0.0",
        "neos/nodetypes": "~3.0.0",
        "neos/seo": "~2.0.0",
        "neos/redirecthandler-neosadapter": "^2.0",
        "neos/redirecthandler-databasestorage": "^2.0",
        "neos/swiftmailer": "~6.0.0",
        "flowpack/simplesearch-contentrepositoryadaptor": "^2.0",        
        "sitegeist/movealong": "1.0.0"
    },
```

Also tried with «^» and «~» in front. Really brute and nasty :speak_no_evil:.

Unfortunately it doesn't work. Obviously I'm fare away to be a Git- or composer-crack. But I guess there is an easier way, then to clone the Package on my own, change the Package-name and require this. (at least I hope)
###Question:

***Is there an easy way to use a better updated package temporarily, until the original has been updated?***
2

You can try to use a commit-sha as version constraint. There is also an option to write “sha as version”.

Btw. I will have a look at sitegeist/movealong soonish.

3

BTW: I just released Sitegeist.MoveAlong 2.0 the pr above was not all that had to be adjusted

4

Thank you,
sitegeist/movealong works great in Neos 3.0.x!

1 Like