summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSam Thursfield <sam.thursfield@codethink.co.uk>2014-09-04 11:54:16 +0100
committerSam Thursfield <sam.thursfield@codethink.co.uk>2014-09-11 13:26:26 +0100
commit27de3db33a5d5ba966657ad436e8434c49757c92 (patch)
tree7bcac4c1dfd73b8fd45a2f4328bcec208dbbbd84
parent199d843c09f1436a3e418ebe9cc572764d75978a (diff)
downloadmorph-27de3db33a5d5ba966657ad436e8434c49757c92.tar.gz
import: Note that custom chunk morphs for each Gem are here to stay
At least for now.
-rwxr-xr-ximport/rubygem.to_chunk6
1 files changed, 5 insertions, 1 deletions
diff --git a/import/rubygem.to_chunk b/import/rubygem.to_chunk
index f1cc0377..f58fd407 100755
--- a/import/rubygem.to_chunk
+++ b/import/rubygem.to_chunk
@@ -329,6 +329,11 @@ class RubyGemChunkMorphologyGenerator
}
]
+ # It'd be rather tricky to include these build instructions as a
+ # BuildSystem implementation in Morph. The problem is that there's no
+ # way for the default commands to know what .gemspec file they should
+ # be building. It doesn't help that the .gemspec may be in a subdirectory
+ # (as in Rails, for example).
build_commands = [
"gem build #{spec.name}.gemspec",
]
@@ -344,7 +349,6 @@ class RubyGemChunkMorphologyGenerator
'kind' => 'chunk',
'description' => description,
'build-system' => 'manual',
- ##'gem-url' => "http://rubygems.org/downloads/#{spec.full_name}.gem",
'products' => split_rules,
'build-commands' => build_commands,
'install-commands' => install_commands,