dpntob9168
2014-02-01 23:26
浏览 110
已采纳

为什么Laravel 4 gitignore composer.lock

Why does the default laravel4 have the composer.lock file included in the .gitignore repo?

It seems to contradict composers recommendations to commit this file into VCS. I was wondering if there was something I didn't know that justified this?

图片转代码服务由CSDN问答提供 功能建议

为什么默认的laravel4包含.gitignore repo中的composer.lock文件?

似乎与作曲家建议相矛盾 将此文件提交到VCS。 我想知道是否有一些我不知道的事情证明了这一点?

  • 写回答
  • 关注问题
  • 收藏
  • 邀请回答

2条回答 默认 最新

  • doupiai5597 2014-02-01 23:49
    已采纳

    According to the author of Laravel here https://github.com/laravel/framework/issues/1412:

    It is recommended for your own apps, not for frameworks.

    已采纳该答案
    打赏 评论
  • dqj29136 2014-04-24 15:13

    It's not clear from the question if you meant the framework or the app. Instead of asking for a clarification, I decided to write this instead for future confused users.

    The problem is, it's ignored not only in the framework but in the app too. The app is what you get when you install Laravel as a project (i.e. not for the purposes of developing it and sending pull requests but for using it in a project of yours).

    In contrast, the Symfony project makes a distinction here and doesn't include the lock file in the .gitignore of the the Symfony Standard Edition distribution (the app) unlike the Symfony framework.

    There are already at least two issues and one pull request regarding composer.lock: issue 1696, issue 2293 and PR 2591.

    打赏 评论

相关推荐 更多相似问题