# # Copyright 2015 YOUR NAME # # All Rights Reserved. # # On Ubuntu systems, we want the ~trusty or ~precise tag at the end of the # version, to allow both .deb files to be included in a single package # directory. I am unaware of how to reliably generate this... other than Ohai. def create_build_iteration base = '1' require 'ohai' s = Ohai::System.new s.all_plugins if s['lsb'] and s['lsb']['codename'] "#{base}~#{s['lsb']['codename']}" else base end end name 'helix-web-services' maintainer 'Perforce Software, Inc. <support+packaging@perforce.com>' homepage 'https://swarm.workshop.perforce.com/projects/perforce-software-helix-web-services/' # Defaults to C:/perforce/helix-web-services on Windows # and /opt/perforce/helix-web-services on all other platforms install_dir "#{default_root}/perforce/#{name}" build_version '2015.1' build_iteration create_build_iteration override :ruby, version: '2.2.2', source: { md5: "326e99ddc75381c7b50c85f7089f3260" } override :ncurses, version: '5.9', source: { md5: "8cb9c412e5f2d96bc6f459aa8c6282a1", url: "http://ftp.gnu.org/gnu/ncurses/ncurses-5.9.tar.gz" } override :rubygems, version: '2.4.5' # If this isn't specified, you get a *very old* version. override :bundler, version: '1.8.9' # Creates required build directories dependency 'preparation' # helix-web-services dependencies/components dependency 'cacerts' dependency 'ruby' dependency 'rubygems' dependency 'bundler' dependency 'helix_web_services' # Version manifest file dependency 'version-manifest' exclude '**/.git' exclude '**/bundler/git' # Configure the license fields for different package types. package :deb do license 'BSD (2-clause)' end package :rpm do license 'BSD (2-clause)' end
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#6 | 18235 | tjuricek | Remove old omnibus packaging logic. | ||
#5 | 17064 | tjuricek |
Correcting file naming schemes use hyphens and supported platform names. Also, moving 'distribution ID' to from the 'build iteration' hack to the .deb logic where it actually works better. |
||
#4 | 17059 | tjuricek | Include the Version file in the tarball, and use that file (if it exists) for the changelist during the package build. | ||
#3 | 17058 | tjuricek |
Alter omnibus build to meet our current naming conventions. The strange bit here is that the 'build_iteration' includes the architecture name on debian, but on rpms, we generate it in the omnibus level. This may confuse people. See also: https://confluence.perforce.com:8443/display/IP/Package+Naming+Approach#PackageNamingApproach-LinuxPackageNamingApproach |
||
#2 | 16285 | tjuricek |
Deploy/install improvements - Include nginx in Omnibus distribution, do not conflict with system nginx install - Use old-school sysvinit scripts - Create 'hws_launch' wrapper to initiate nginx and unicorn, which also reads system config file for settings |
||
#1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
//guest/perforce_software/helix-web-services/main/packaging/omnibus-helix-web-services/config/projects/helix-web-services.rb | |||||
#7 | 15603 | tjuricek | Trying another approach to handling the cacerts breakage. | ||
#6 | 15602 | tjuricek | Updating the cacerts dependency for omnibus builds. | ||
#5 | 15462 | tjuricek | Explicitly set ncurses version to 5.9, which it was before someone decided to use a different version that no longer exists. | ||
#4 | 15238 | tjuricek |
Set license to 2-clause BSD (similar to p4ruby) P4WEBAPI-116 |
||
#3 | 15237 | tjuricek |
Change the maintainer to company standard. I *believe* this will edit the correct fields in the right places. |
||
#2 | 15236 | tjuricek |
Using the platform codename (if it exists) in the build_iteration value. This allows us to store multiple .deb files in the same package repo for Ubuntu 12 vs Ubuntu 14, etc. |
||
#1 | 14794 | tjuricek |
Omnibus installation framework. Right now, this mostly just packages up most of the software for use within an embedded ruby distribution. Not everything is working because there are decisions to make I'm not entirely sure about. Things, like, "do we embed postgres", or "do I embed unicorn and generate a stupid init.d script". |