1

I'm making a gem called something like ugly_fork_of_foo. Can I add something to my gemspec to tell the system that ugly_fork_of_foo conflicts with foo, that both can't be installed simultaneously?

Mark Thomas
  • 37,131
  • 11
  • 74
  • 101
Bryan Larsen
  • 9,468
  • 8
  • 56
  • 46
  • I suppose I could make a gem called `ugly_monkeypatches_for_foo` instead, but I think that `ugly_fork_of_foo` is more appropriate here. Both are ugly, though! – Bryan Larsen Oct 07 '12 at 11:54
  • Can you make it a non-ugly feature and submit a pull request? – Mark Thomas Oct 07 '12 at 13:24
  • No, I've tried, but it's too specific a feature to push upstream. Luckily I think Rails 4 is going to make it unnecessary so it'll just be a shim for those running Rails 3 in the future. – Bryan Larsen Oct 09 '12 at 13:16
  • Can somebody with enough karma reject the edit? It introduced a capitalization error, and quoted stuff I deliberately left unquoted because it's unnecessary emphasis. Thanks. – Bryan Larsen Oct 09 '12 at 13:21

1 Answers1

1

As far as I know you can't define conflicts in gemspec.

marcgg
  • 65,020
  • 52
  • 178
  • 231