clenver 0.1.9 → 0.1.10

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    MDRlZjU0OGVjZjQ0ZDRlN2UyNDRkZWIxZGI3YmY3ZjY1MDUyZGIwOQ==
-  data.tar.gz: !binary |-
-    OWJjNzk2MTUyMmRjOTg5NWE4ZGJkZTZkZmZjYmI1ZWFjMmVkYzU5OQ==
+SHA1:
+  metadata.gz: df349ceb9945165a4bf0f2c5e6258e8335544a79
+  data.tar.gz: 9f1362e7e826c8329987bf4f701e31a7d017f69a
 SHA512:
-  metadata.gz: !binary |-
-    Y2NlYjljNTMzN2ZmNTRkNzA3ZjkxMTMwMzNlMTE4OTIyNzk3NWE1MThlMWI3
-    ODIxZTg0YThmMzE2MWI3NjIwZjQyYjY2MTMyNzRkYTEzYzYxNDNjODFhYjBi
-    MzczM2U0N2UwODcwNGNlOTk1ZjRhZDg2NzBjOTQ4NDhmNDk2YjU=
-  data.tar.gz: !binary |-
-    OGU0ZjNmN2NiMDM5ZmUwYzE0OTEwMTFlOGMxNjBiODY3Mjc2YjE1MjAzMzQ3
-    NGFlODM0ZDZiNTY4ZjJiNDc2Y2M1MDgxZjBjZTc0NDFjZTk1ZDI1MGMxNDli
-    YWNlZmY2OGEwZTU3NGE0YzM1ZWQwMjI3MzQxOGU0MmI4Zjc3OWY=
+  metadata.gz: 59fc7a9e72442f9a98e40cf9a949e55b68b8fe9627c7a06b1e890a9b49814304f95ecfd94c8116fcda4dc94866fe1446436f613c12f474c5c08d0a9e52012a90
+  data.tar.gz: 12efe8b91b05f0a7cb425fb7f49abbb52e02dcb6fd1a609687388bfc202cc322f539ba054e3717777ee5e07fa36eaaa98e7e17678cc9580a069d38952a2e3659

data/.gitignore

@@ -0,0 +1,18 @@
+*.gem
+*.rbc
+.bundle
+.config
+coverage
+InstalledFiles
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp
+
+# YARD artifacts
+.yardoc
+_yardoc
+doc/

data/.travis.yml

@@ -0,0 +1,4 @@
+language: ruby
+rvm:
+    - 1.9.3
+    - 2.0.0

data/Gemfile

@@ -0,0 +1,3 @@
+source 'https://rubygems.org'
+gem 'coveralls', require: false
+gemspec

data/Gemfile.lock

@@ -0,0 +1,65 @@
+PATH
+  remote: .
+  specs:
+    clenver (0.1.10)
+      git (= 1.2.6)
+      gli (= 2.8.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    aruba (0.5.3)
+      childprocess (>= 0.3.6)
+      cucumber (>= 1.1.1)
+      rspec-expectations (>= 2.7.0)
+    builder (3.2.2)
+    childprocess (0.3.9)
+      ffi (~> 1.0, >= 1.0.11)
+    coveralls (0.7.0)
+      multi_json (~> 1.3)
+      rest-client
+      simplecov (>= 0.7)
+      term-ansicolor
+      thor
+    cucumber (1.3.8)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.3)
+      gherkin (~> 2.12.1)
+      multi_json (>= 1.7.5, < 2.0)
+      multi_test (>= 0.0.2)
+    diff-lcs (1.2.4)
+    ffi (1.9.0)
+    gherkin (2.12.1)
+      multi_json (~> 1.3)
+    git (1.2.6)
+    gli (2.8.0)
+    json (1.8.0)
+    mime-types (1.25)
+    multi_json (1.8.1)
+    multi_test (0.0.2)
+    rake (10.1.0)
+    rdoc (4.0.1)
+      json (~> 1.4)
+    rest-client (1.6.7)
+      mime-types (>= 1.16)
+    rspec-expectations (2.14.3)
+      diff-lcs (>= 1.1.3, < 2.0)
+    simplecov (0.7.1)
+      multi_json (~> 1.0)
+      simplecov-html (~> 0.7.1)
+    simplecov-html (0.7.1)
+    term-ansicolor (1.2.2)
+      tins (~> 0.8)
+    thor (0.18.1)
+    tins (0.11.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  aruba
+  clenver!
+  coveralls
+  rake
+  rdoc
+  rspec-expectations

data/LICENSE

@@ -0,0 +1,339 @@
+GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    Command Line Home Environment Manger
+    Copyright (C) 2013  Piotr Król
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  {signature of Ty Coon}, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.

data/README.md

@@ -0,0 +1,56 @@
+clenver
+=======
+[![Gem Version](https://badge.fury.io/rb/clenver.png)](http://badge.fury.io/rb/clenver) [![Build Status](https://travis-ci.org/pietrushnic/clenver.png?branch=master)](https://travis-ci.org/pietrushnic/clenver) [![Code Climate](https://codeclimate.com/github/pietrushnic/clenver.png)](https://codeclimate.com/github/pietrushnic/clenver) [![Coverage Status](https://coveralls.io/repos/pietrushnic/clenver/badge.png)](https://coveralls.io/r/pietrushnic/clenver)
+
+clenver (Command Line home ENVironment mangER) is a Ruby gem that bootstrap and manage your shell environment. 
+
+## Introduction
+
+clenver aims to shorten time of configuring your brand new Linux account to fully featured development envionment of your choice by using:
+* VCS (version control system) repositories
+* directory creation
+* symlinking
+
+It also aims to reliably manage your exising environment by:
+* easy switching between project workspaces
+* report on the status of used repositories (like [oh-my-zsh](), [spf13-vim](), ...)
+
+## Installation
+Simply type in you shell:
+```
+gem install clenver
+```
+## Getting Started
+### Bootstrap
+clenver is able to bootstrap your brand new Linux account according to rules provided through YAML file. For 
+xample create `dummy.yml` with below content:
+```yaml
+https://github.com/pietrushnic/dummy.git:
+  links:
+    foobar.txt:
+    - foobar_link
+    foobar:
+    - foobar_dir_link
+  run:
+    - echo "success!!!"
+  remotes:
+    upstream:
+    - https://github.com/pietrushnic/dummy.git
+```
+After that running
+```
+clenver init dummy.yaml
+```
+gives you below tree:
+```
+dummy
+├── dummy
+│   ├── foobar
+│   ├── foobar.txt
+│   └── README.md
+├── foobar_dir_link -> $PWD/dummy/dummy/foobar
+└── foobar_link -> $PWD/dummy/dummy/foobar.txt
+```
+And of course will display `success!!!` message. Carefully crafted YAML file can bootstrap you clean user account into fully configured user account.
+## Examples
+## Contribution

data/Rakefile

@@ -0,0 +1,44 @@
+require 'rake/clean'
+require 'rubygems'
+require 'rubygems/package_task'
+require 'rdoc/task'
+require 'cucumber'
+require 'cucumber/rake/task'
+Rake::RDocTask.new do |rd|
+  rd.main = "README.rdoc"
+  rd.rdoc_files.include("README.rdoc","lib/**/*.rb","bin/**/*")
+  rd.title = 'Your application title'
+end
+
+spec = eval(File.read('clenver.gemspec'))
+
+Gem::PackageTask.new(spec) do |pkg|
+end
+CUKE_RESULTS = 'results.html'
+CLEAN << CUKE_RESULTS
+desc 'Run features'
+Cucumber::Rake::Task.new(:features) do |t|
+  opts = "features --format html -o #{CUKE_RESULTS} --format progress -x"
+  opts += " --tags #{ENV['TAGS']}" if ENV['TAGS']
+  t.cucumber_opts =  opts
+  t.fork = false
+end
+
+desc 'Run features tagged as work-in-progress (@wip)'
+Cucumber::Rake::Task.new('features:wip') do |t|
+  tag_opts = ' --tags ~@pending'
+  tag_opts = ' --tags @wip'
+  t.cucumber_opts = "features --format html -o #{CUKE_RESULTS} --format pretty -x -s#{tag_opts}"
+  t.fork = false
+end
+
+task :cucumber => :features
+task 'cucumber:wip' => 'features:wip'
+task :wip => 'features:wip'
+require 'rake/testtask'
+Rake::TestTask.new do |t|
+  t.libs << "test"
+  t.test_files = FileList['test/*_test.rb']
+end
+
+task :default => [:test,:features]

data/binscripts/clenver-installer

@@ -0,0 +1,6 @@
+#!/usr/bin/env bash
+sudo apt-get -y install curl git
+curl -L https://get.rvm.io | bash -s stable --ruby
+source $HOME/.rvm/scripts/rvm
+rvm use ruby
+gem install clenver

data/clenver.gemspec

@@ -0,0 +1,29 @@
+# Ensure we require the local version and not one we might have installed already
+require File.join([File.dirname(__FILE__),'lib','clenver','version.rb'])
+spec = Gem::Specification.new do |s| 
+  s.name = 'clenver'
+  s.version = Clenver::VERSION
+  s.author = 'Piotr Król'
+  s.email = 'pietrushnic@gmail.com'
+  s.homepage = 'https://github.com/pietrushnic/clenver'
+  s.platform = Gem::Platform::RUBY
+  s.summary = 'Command line home directory manager'
+  s.license = 'GPLv2'
+  s.description = 'clenver aims to shorten time of configuring your brand new *NIX account to fully featured development envionment of your choice'
+# Add your other files here if you make them
+  s.files = `git ls-files`.split("\n")
+  s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
+  s.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+  s.require_paths << 'lib'
+  s.has_rdoc = true
+  s.extra_rdoc_files = ['README.rdoc','clenver.rdoc']
+  s.rdoc_options << '--title' << 'clenver' << '--main' << 'README.rdoc' << '-ri'
+  s.bindir = 'bin'
+  s.executables << 'clenver'
+  s.add_development_dependency('rake')
+  s.add_development_dependency('rdoc')
+  s.add_development_dependency('aruba')
+  s.add_development_dependency('rspec-expectations')
+  s.add_runtime_dependency('gli','2.8.0')
+  s.add_runtime_dependency('git','1.2.6')
+end

data/features/clenver.feature

@@ -0,0 +1,8 @@
+Feature: My bootstrapped app kinda works
+  In order to get going on coding my awesome app
+  I want to have aruba and cucumber setup
+  So I don't have to do it myself
+
+  Scenario: App just runs
+    When I get help for "clenver"
+    Then the exit status should be 0

data/features/clenver_init.feature

@@ -0,0 +1,184 @@
+Feature: Initialization
+  In order to save time and money
+  User should be able to bootstrap project environment ASAP
+
+  Scenario: Given config file doesn't exist
+    When I run `clenver init no_name.yml`
+    Then the exit status should be 2
+
+  Scenario: Valid config file given
+    Given The default aruba timeout is 10 seconds
+    Given a file named "valid.yml" with:
+    """
+    https://github.com/pietrushnic/dummy.git:
+      links:
+        foobar.txt:
+        - foobar_link
+        foobar:
+        - foobar_dir_link
+    """
+    When I run `clenver init valid.yml`
+    Then the exit status should be 0
+
+  Scenario: Invalid config file given
+    Given a file named "invalid.yml" with:
+    """
+    Lorem:{]}
+    ipsum:
+    dolor: sit amet,
+    consectetur adipisicing elit, sed: do eiusmod tempor
+    incididunt: ut
+    labore et dolore: magna aliqua.
+    """
+    When I run `clenver init invalid.yml`
+    Then the exit status should be 1
+
+  Scenario: Init simple project (repo w/ colon)
+    Given The default aruba timeout is 10 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    https://github.com/pietrushnic/dummy.git:
+    """
+    When I run `clenver init test_repo.yml`
+    Then the following files should exist:
+      | test_repo/dummy/README.md |
+
+  Scenario: Init simple project (repo w/o colon)
+    Given The default aruba timeout is 10 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    https://github.com/pietrushnic/dummy.git
+    """
+    When I run `clenver init test_repo.yml`
+    Then the following files should exist:
+      | test_repo/dummy/README.md |
+
+  Scenario: Init simple project to given directory
+    Given The default aruba timeout is 10 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    https://github.com/pietrushnic/dummy.git:
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the following files should exist:
+      | some_tmp/test_repo/dummy/README.md |
+
+   Scenario: Init project with symbolic links
+    Given The default aruba timeout is 10 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    https://github.com/pietrushnic/dummy.git:
+      links:
+        foobar.txt:
+        - foobar_link
+        foobar:
+        - foobar_dir_link
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the following links should exist:
+      | some_tmp/test_repo/foobar_link     |
+      | some_tmp/test_repo/foobar_dir_link |
+
+   Scenario: use system variable in path
+    Given The default aruba timeout is 10 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    https://github.com/pietrushnic/dummy.git:
+      links:
+        $HOME/foobar.txt:
+        - $HOME/foobar_link
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the following links should exist:
+      | $HOME/foobar_link     |
+
+  Scenario: Connect remote and check uri
+    Given The default aruba timeout is 25 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    https://github.com/pietrushnic/spf13-vim.git:
+      remotes:
+        upstream:
+        - https://github.com/spf13/spf13-vim.git
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the following remote uris should be connected in "some_tmp/test_repo/spf13-vim":
+      | https://github.com/spf13/spf13-vim.git |
+
+  Scenario: Connect remote and check its name
+    Given The default aruba timeout is 25 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    https://github.com/pietrushnic/spf13-vim.git:
+      remotes:
+        upstream:
+        - https://github.com/spf13/spf13-vim.git
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the following remote branches should be connected in "some_tmp/test_repo/spf13-vim":
+      | upstream |
+
+  Scenario: run simple command
+    Given The default aruba timeout is 10 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    https://github.com/pietrushnic/dummy.git:
+      run:
+        - echo "success!!!!"
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the output should contain "success!!!!\n"
+
+  Scenario: apt: check if package installed
+    Given The default aruba timeout is 10 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    apt:
+      - vim
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the output should contain "vim is already the newest version.\n"
+
+  Scenario: package installed and simple command run
+    Given The default aruba timeout is 10 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    apt:
+      - vim
+    https://github.com/pietrushnic/dummy.git:
+      run:
+        - echo "success!!!!"
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the output should contain "vim is already the newest version.\n"
+    Then the output should contain "success!!!!\n"
+
+  Scenario: install gem
+    Given The default aruba timeout is 45 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    gem:
+      - tmuxinator
+    https://github.com/pietrushnic/dummy.git:
+      run:
+        - echo "success!!!!"
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the output should contain "installed\n"
+    Then the output should contain "success!!!!\n"
+  @wip
+  Scenario: install gem and package
+    Given The default aruba timeout is 45 seconds
+    Given a file named "test_repo.yml" with:
+    """
+    apt:
+      - vim
+    gem:
+      - tmuxinator
+    https://github.com/pietrushnic/dummy.git:
+      run:
+        - echo "success!!!!"
+    """
+    When I run `clenver init test_repo.yml some_tmp`
+    Then the output should contain "installed\n"
+    Then the output should contain "success!!!!\n"

data/features/step_definitions/clenver_steps.rb

@@ -0,0 +1,30 @@
+require 'rspec/expectations'
+require 'clenver/link'
+
+When /^I get help for "([^"]*)"$/ do |app_name|
+  @app_name = app_name
+  step %(I run `#{app_name} help`)
+end
+
+# Add more step definitions here
+
+Then(/^the following links should exist:$/) do |files|
+  files.raw.map{|file_row| file_row[0]}.each do |f|
+    if /\$\w+/.match(f)
+      f_path = %x[ echo #{f}].strip
+    elsif
+      f_path = "tmp/aruba/" + f
+    end
+    File.should be_symlink(f_path)
+  end
+end
+
+Then(/^the following remote (?:uris|branches) should be connected in "(.*?)":$/) do |arg1, table|
+  table.raw.map{|repo| repo[0]}.each do |r|
+    curr_pwd = Dir::pwd
+    Dir::chdir("tmp/aruba" + "/" + arg1)
+    res = %x[git remote -v| grep #{r}|wc -l].strip
+    Dir::chdir(curr_pwd)
+    res.to_i.should eq(2)
+  end
+end

data/features/support/env.rb

@@ -0,0 +1,17 @@
+require 'coveralls'
+Coveralls.wear!
+require 'aruba/cucumber'
+
+ENV['PATH'] = "#{File.expand_path(File.dirname(__FILE__) + '/../../bin')}#{File::PATH_SEPARATOR}#{ENV['PATH']}"
+LIB_DIR = File.join(File.expand_path(File.dirname(__FILE__)),'..','..','lib')
+
+Before do
+  # Using "announce" causes massive warnings on 1.9.2
+  @puts = true
+  @original_rubylib = ENV['RUBYLIB']
+  ENV['RUBYLIB'] = LIB_DIR + File::PATH_SEPARATOR + ENV['RUBYLIB'].to_s
+end
+
+After do
+  ENV['RUBYLIB'] = @original_rubylib
+end

data/lib/clenver/package_manager.rb

@@ -0,0 +1,19 @@
+class PackageManger
+  def initialize(name, pkgs)
+    @name = name
+    @pkgs = pkgs
+  end
+
+  def install()
+    case @name
+    when 'apt'
+      out = %x[sudo apt-get install #{@pkgs}]
+    when 'gem'
+      out = %x[gem install #{@pkgs}]
+    end
+    puts out
+  end
+
+  def check(pkg)
+  end
+end

data/lib/clenver/project.rb

@@ -30,6 +30,9 @@ class Project
     when Hash
       @repos.each do |uri, content|
         #TODO: verify if r is a supported repo
+        if uri == 'apt' or uri == 'gem'
+          next
+        end
         begin
           r = Repository.new(uri, dst)
           r.clone

data/lib/clenver/runner.rb

@@ -2,6 +2,7 @@ require 'gli'
 require 'clenver'
 require 'clenver/project'
 require 'clenver/logging'
+require 'clenver/package_manager'
 
 module Clenver
   class Runner
@@ -19,6 +20,22 @@ module Clenver
           logger.debug("yaml: #{yaml}")
           #TODO: create test and fix this place with check for empty file
           p = Project.new(File.basename("#{@path}", ".yml"), yaml, @dst)
+          unless yaml['apt'].nil?
+            for pkg in yaml['apt'] do
+              pkgs = pkg + " "
+            end
+            puts pkgs
+            p_mgr = PackageManger.new('apt', pkgs)
+            p_mgr.install()
+          end
+          unless yaml['gem'].nil?
+            for pkg in yaml['gem'] do
+              pkgs = pkg + " "
+            end
+            puts pkgs
+            p_mgr = PackageManger.new('gem', pkgs)
+            p_mgr.install()
+          end
           p.create_repos
           p.init_project
         rescue Psych::SyntaxError => ex

data/lib/clenver/version.rb

@@ -1,3 +1,3 @@
 module Clenver
-  VERSION = '0.1.9'
+  VERSION = '0.1.10'
 end

data/test/default_test.rb

@@ -0,0 +1,14 @@
+require 'test_helper'
+
+class DefaultTest < Test::Unit::TestCase
+
+  def setup
+  end
+
+  def teardown
+  end
+
+  def test_the_truth
+    assert true
+  end
+end

data/test/test_helper.rb

@@ -0,0 +1,9 @@
+require 'test/unit'
+
+# Add test libraries you want to use here, e.g. mocha
+
+class Test::Unit::TestCase
+
+  # Add global extensions to the test case class here
+  
+end

data/test/vbox/regression.sh

@@ -0,0 +1,81 @@
+#!/bin/bash
+#TODO: write documentation and disclaimer about vm usage
+#TODO: make sure that $1 exist - use vboxmanage list
+SCANCODES=$HOME/src/scancodes/scancodes
+pub_key=$(cat $HOME/.ssh/id_rsa.pub)
+pkey_scancodes=$(echo -en $pub_key|$SCANCODES)
+
+sc_send () {
+    for (( i=0; i<${#2}; i++ )); do
+        echo ">${2:$i:1}<"
+        c=$(echo -en "${2:$i:1}"|$SCANCODES)
+        echo "$1: send ${c}"
+        vboxmanage controlvm $1 keyboardputscancode $c
+        if [[ $i -eq $(expr ${#2} - 1) ]]; then
+            c=$(echo -en "\n"|$SCANCODES)
+            echo "$1: send ${c}"
+            vboxmanage controlvm $1 keyboardputscancode $c
+        fi
+    done
+}
+
+startvm() {
+    echo "startvm $1"
+    vboxmanage startvm $1 # -type headless
+}
+
+ssh_cmd () {
+    ssh -oStrictHostKeyChecking=no user@localhost -p 2222 $1
+}
+
+scp_cmd () {
+    scp -P 2222 -oStrictHostKeyChecking=no $1 user@localhost:$2
+}
+
+bash_cmd () {
+    ssh_cmd "bash -l -c $1"
+}
+
+no_pass_ssh () {
+    startvm $1
+    sleep 3
+    vboxmanage controlvm $1 keyboardputscancode 1C 9C
+    sleep 45
+    # cat host pub key to guest .ssh/authorized_keys
+    sc_send $1 'mkdir -p $HOME/.ssh'
+    st_pt=' > $HOME/.ssh/authorized_keys'
+    nd_pt="echo $pub_key"
+    echo "$nd_pt$st_pt"
+    sc_send $1 "$nd_pt$st_pt"
+}
+
+clenver_install() {
+    no_pass_ssh $1
+    if [[ $# -ge 2 ]]; then
+        cat $2 | while read line; do
+            sc_send $1 "$line"
+        done
+    else
+        ssh_cmd 'wget -O - bit.ly/1hASabs|bash'
+        ssh_cmd 'bash -l -c "clenver"'
+    fi
+}
+
+init_general () {
+   clenver_install $1
+   #ssh_cmd 'bash -l -c "clenver init http://bit.ly/1cpqEqp"'
+   ssh_cmd 'git clone https://github.com/pietrushnic/clenver_projects.git src/clenver_projects'
+   ssh_cmd 'bash -l -c "clenver init src/clenver_projects/general.yml"'
+}
+
+init_custom () {
+    no_pass_ssh $1
+    scp_cmd $2 /home/user
+    home_v='$HOME'
+    nd_pt="/${2##*/}"
+    bash_cmd "$home_v$nd_pt"
+    ssh_cmd "git clone https://github.com/pietrushnic/clenver_projects.git src/clenver_projects"
+    bash_cmd "clenver init $home_v/src/clenver_projects/general.yml"
+}
+
+eval "$@"

metadata

@@ -1,69 +1,69 @@
 --- !ruby/object:Gem::Specification
 name: clenver
 version: !ruby/object:Gem::Version
-  version: 0.1.9
+  version: 0.1.10
 platform: ruby
 authors:
 - Piotr Król
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-10-30 00:00:00.000000000 Z
+date: 2013-11-15 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rdoc
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: aruba
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
   name: rspec-expectations
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ! '>='
+    - - '>='
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
@@ -104,17 +104,34 @@ extra_rdoc_files:
 - README.rdoc
 - clenver.rdoc
 files:
+- .gitignore
+- .travis.yml
+- Gemfile
+- Gemfile.lock
+- LICENSE
+- README.md
+- README.rdoc
+- Rakefile
 - bin/clenver
-- lib/clenver/version.rb
+- binscripts/clenver-installer
+- clenver.gemspec
+- clenver.rdoc
+- features/clenver.feature
+- features/clenver_init.feature
+- features/step_definitions/clenver_steps.rb
+- features/support/env.rb
+- lib/clenver.rb
+- lib/clenver/assets/sample.yml
+- lib/clenver/link.rb
+- lib/clenver/logging.rb
+- lib/clenver/package_manager.rb
 - lib/clenver/project.rb
 - lib/clenver/repository.rb
-- lib/clenver/link.rb
 - lib/clenver/runner.rb
-- lib/clenver/logging.rb
-- lib/clenver/assets/sample.yml
-- lib/clenver.rb
-- README.rdoc
-- clenver.rdoc
+- lib/clenver/version.rb
+- test/default_test.rb
+- test/test_helper.rb
+- test/vbox/regression.sh
 homepage: https://github.com/pietrushnic/clenver
 licenses:
 - GPLv2
@@ -131,17 +148,17 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.1.9
+rubygems_version: 2.1.5
 signing_key: 
 specification_version: 4
 summary: Command line home directory manager