1. 04 Aug, 2017 1 commit
  2. 30 Sep, 2016 1 commit
  3. 20 May, 2016 1 commit
  4. 08 Apr, 2016 1 commit
  5. 24 Mar, 2016 1 commit
  6. 15 Mar, 2016 1 commit
    • James Casey's avatar
      This adds license reporting to omnibus: · 16dd5419
      James Casey authored
      * Add license & license_file DSL methods to software.
        * license (String): Sets the license of the software component.
        * license_file (String): The relative path or the url of the license file of the software to be included in LICENSES directory.
          * Can be used multiple times.
          * You can use :project_license as a special value if the software is build related code and if it is using project's license.
      * Add license, license_file and license_file_path DSL methods to project.
        * license (String): Sets the license of the project.
        * license_file (String): The relative path or the url of the license file of the project to be included in the file that will be created at project.license_file_path.
        * license_file_path (String): The relative path of the main license file that will be created for the project. Default: LICENSE.
      
      With this omnibus will:
      1. Collect all the license files specified in software components into install_dir/LICENSES directory.
      2. Create a license file at install_dir/LICENSE which will contain license of the project and license information for all the software components that are being included.
      16dd5419
  7. 10 Mar, 2015 2 commits
  8. 23 Feb, 2015 1 commit
    • Steven Danna's avatar
      Refactor manifest handling · 7c82b529
      Steven Danna authored
      This changeset attempts to reduce the number of places that behavior
      substantively changes based on the presence of an external manifest or
      not.  Key changes include
      
      - Fetchers now take a manifest entry in their constructor.  The
        manifest has no knowledge of how the entry was created and doesn't
        care.
      
      - Fetchers expect a fully resolved version in the manifest entry.
        Users can construct such a version using the
        #resolve_version(source, version) functions
      
      - Omnibus::Project only interacts with the manifest in 2 ways: (1)
        passes it to the Software when constructing software objects, and
        (2) polling the software collection for their manifest entries to
        present it to the user.
      
      - Omnibus::Software contains the main interaction with the manifest.
        When constructing a Fetcher, it passes its own manifest entry.
        Omnibus::Software#manifest_entry is now the only substantive place
        in the code where we do something different based on whether the
        user provided a manifest entry or not.
      7c82b529
  9. 22 Aug, 2014 2 commits
  10. 19 Aug, 2014 2 commits
  11. 13 Aug, 2014 2 commits
  12. 06 Aug, 2014 2 commits
  13. 04 Aug, 2014 11 commits
  14. 26 Jul, 2014 1 commit
  15. 25 Jul, 2014 2 commits
  16. 24 Jul, 2014 9 commits