使用 Bundler 进行 Gem 开发：包含还是排除 Gemfile？

发布于 2024-10-07 22:52:45 字数 530 浏览 0 评论 0原文

我正在本地开发一个 gem。它是一个只有测试依赖项的命令行实用程序，我的 Gemfile 如下所示：

source :rubygems
gemspec

group :test do
  gem "cucumber"
  gem "aruba"
  gem "rspec"
end

我的 gemspec 如下所示：

Gem::Specification.new do |s|
  # authorship stuff...
  s.files = `git ls-files`.split("\n")
end

这是 Bundler 创建的默认 gemspec。我知道我们应该将 Gemfile 和 Gemfile.lock 保留在源代码管理中，但我想知道如何通过 Gem::Specification#files 属性将它们包含在打包的 gem 中。是否有支持/反对在分布式 gem 中包含 Gemfile 和 Gemfile.lock 的争论？这对我来说似乎很奇怪或者至少没有必要。

原文

I'm developing a gem locally. It's a command-line utility that only has test dependencies, and my Gemfile looks like this:

source :rubygems
gemspec

group :test do
  gem "cucumber"
  gem "aruba"
  gem "rspec"
end

My gemspec looks like this:

Gem::Specification.new do |s|
  # authorship stuff...
  s.files = `git ls-files`.split("\n")
end

That's the default gemspec created by Bundler. I know we're supposed to keep Gemfile and Gemfile.lock in source control, but I'm wondering about including them in the packaged gem through the Gem::Specification#files attribute. Are there arguments for/against including Gemfile and Gemfile.lock in the distributed gem? It seems weird or at least unnecessary to me.

分享到QQ

分享到微博