# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#6 | 18235 | tjuricek | Remove old omnibus packaging logic. | ||
#5 | 17099 | tjuricek |
Extract tarballs before running package commands. Tar seems to preserve a lot of file permissions our tools do not by default, and there's too many (10k) for me to efficiently handle. |
||
#4 | 17094 | tjuricek |
Revising omnibus build to expose license files, and embed sources By default a 'liceneses' directory will contain copies of the license files included with each of our projects we build or include in the installed product. The sources for the omnibus build will no longer get downloaded for each build. This should alleviate build failures, and make it easier to review source licenses. This may require some xorg-macros library to be available for ./configure scripts. |
||
#3 | 17093 | tjuricek |
Removed omnibus-software dependencies, in preparing for license compliance. This removes our external dependency on the omnibus-software project in Gitlab. To make it easier to maintain license compliance for compiled libraries, the omnibus software configurations will be edited to copy appropriate LICENSE files into the distributed packages. |
||
#2 | 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 |
||
#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/software/ruby.rb | |||||
#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". |