Yep... It's dead wrong for anybody to be getting extensions directly from a git repository. Remember git is a repository for a project under development where other people can collaborate with the developer. As the download links usually say, it's the "source code".david63 wrote:So far there have not been many extensions that have needed these dependencies and we have got ourselves (rightly or wrongly) into using Git as a means of accessing extensions in development.
Users should only ever install a released product. That's why, as Paul suggests, ext developers can make releases on their repo, and they can even upload the properly packaged distribution zips to those releases, so users download the right thing, easy to install, without having to tell them to rename folders or worse, run build scripts.
Never do #1. As for #2 well, sure people should do that if they want to collaborate with you on your project.david63 wrote:I agree that expecting many users to "compile" with composer (most probably do not know what Composer is) in order to test and develop extensions is not ideal. As I see it there are three options:
1. Include vendor in Git
2. Don't include vendor in Git and expect users to use Composer
3. Have a download at some other place that includes vendor
Composer is easy to install in Xampp
#3 is the way to go, using Git tags and releases, just as we do:
https://github.com/phpbb-extensions/col ... s/releases