From a376158b5a8be391f435bd2812b90f13757e01e7 Mon Sep 17 00:00:00 2001
From: schneems <richard.schneeman+foo@gmail.com>
Date: Thu, 28 Apr 2022 14:35:35 -0500
Subject: [PATCH] Fix default gem require error

When vendoring a default gem in the Ruby repository it uses a different path structure:

```
$ tool/sync_default_gems.rb dead_end
Sync zombocom/dead_end
```

This causes an error in the gemspec when trying to require a relative file. To overcome this error, other default gems will try to require the expected location and then fallback to a different path such as https://github.com/ruby/error_highlight/blob/f88b6fab2ff34559a0f08d019d574dbb52426a20/error_highlight.gemspec#L4-L8
---
 dead_end.gemspec | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/dead_end.gemspec b/dead_end.gemspec
index 06bc030..4268ea7 100644
--- a/dead_end.gemspec
+++ b/dead_end.gemspec
@@ -1,6 +1,10 @@
 # frozen_string_literal: true
 
-require_relative "lib/dead_end/version"
+begin
+  require_relative "lib/dead_end/version"
+rescue LoadError # Fallback to load version file in ruby core repository
+  require_relative "version"
+end
 
 Gem::Specification.new do |spec|
   spec.name = "dead_end"