Fix some issues with using scm url with collections from the cli.
Change the scm archive building code to not include a top dir
Fix the way RequirementSpec would get it's spec_string populated
Add 'scm' back to RequirementSpec, since we need to know the scm type to
later build the right url for archive since the git+https://github.com/alikins/whatever
style isnt understood by git, git-archive, or the scm_archive module
Fixes part of the issue reported in #236 for now.
Long term, may just remove scm_url support entirely, or at least not support it except for
semver version tags.
Related: #236
ISSUE TYPE
Feature Pull Request
Bugfix Pull Request
MAZER VERSION
name = mazer
version = 0.4.0
config_file = /home/adrian/.ansible/mazer.yml
uname = Linux, newswoop, 5.0.5-200.fc29.x86_64, #1 SMP Wed Mar 27 20:58:04 UTC 2019, x86_64
executable_location = /home/adrian/venvs/mazer_0.4.0_py36/bin/mazer
python_version = 3.6.8 (default, Jan 27 2019, 09:00:23) [GCC 8.2.1 20181215 (Red Hat 8.2.1-6)]
python_executable = /home/adrian/venvs/mazer_0.4.0_py36/bin/python
SUMMARY
Fix some issues with using scm url with collections from the cli.
git+https://github.com/alikins/whateverstyle isnt understood by git, git-archive, or the scm_archive moduleFixes part of the issue reported in #236 for now.
Long term, may just remove scm_url support entirely, or at least not support it except for semver version tags.
Related: #236
ISSUE TYPE
MAZER VERSION
ADDITIONAL INFORMATION