Package Name on Github vs Packagist

[xLink]

These should really be sync'd up, having them as different things makes it hard to overload the package with the custom one as the names are different and composer has no way to overloading yours with a custom one if the names are different.

('toddish/verify' !== 'toddish/verify-l4')

[Toddish]

Good point!

I think for clarity's sake, the package should be renamed verify-l4, and the old Laravel 3 bundle be renamed to verify-l3. This'll at least 'future proof' it a little.

Sound OK?

[xLink]

sounds like a plan!

[Toddish]

Had a look into this, and there's no way to rename a package nicely. Renaming it will mean losing all it's stats, which isn't a massive deal, but pretty annoying.

Is the overloading of the package a big deal? Can it be done, and is it just a bit of a pain?

If it's not too bad, I could add a section in the docs about it.

[xLink]

composer does it by the name of the repo, which in this case isnt the same of the package name so it cant be overloaded afaik

[Toddish]

This should hopefully be sorted soon :)