class P4 Version = VERSION = '2014.2.0.gem4' end
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#14 | 14754 | tjuricek |
Fall back to hard-coded p4ruby version strings. While a little bit more work, our tools don't really account for filenames with version numbers in them. Additionally, this avoids having lots of files hanging around just because we've tested p4ruby against updates to dependencies (the p4api). Releases should be *very* rare, and the general rule is just to update the version whenever you make a release to rubygems. |
||
#13 | 14749 | tjuricek | Fix reference to ENV hash | ||
#12 | 14748 | tjuricek |
The 'branch' specifier in Version files are illegal Ruby versions; use the CODELINE environment var instead. Remove the 'doc/' ignore from the .gitignore file |
||
#11 | 14747 | tjuricek |
Deriving the p4ruby version from version strings generated by engtools. For main/prep branches, the version string is: [YEAR].[REL].0.[BRANCH][CHANGELIST]. This should allow people to depend on something like '~> 2015.1.0.main' or '~> 2015.1.0.prep' for any prereleases we make to Rubygems. For release branches, the version string is [YEAR].[REL].[CHANGELIST]. Then, you can just depend on '~> 2015.1' for production releases. I may not automate prereleases directly into Rubygems (there will be a lot of them because of the p4api dependency). |
||
#10 | 14737 | tjuricek |
Change the version string to match the 'codeline' for non-production builds. How Ruby gems are versioned are pretty different than our internal scheme. We should generally only update the version string after public releases, which should be rare. |
||
#9 | 14721 | tjuricek | Updating to the 2015.1 branch of the workshop code, just to avoid the different spec map and version string | ||
#8 | 14719 | tjuricek |
Mirroring the current state of the workshop. From this point, we will try to rebuild the history of p4-ruby in the workshop from this codeline. |
||
#7 | 14717 | tjuricek |
2014.2.0.pre6 - Documenting override parameters to gem install for OS X default system ruby users Please note: after investigating this issue, I would not recommend using the default system Ruby under OS X. P4RUBY-181 Imported from Git Author: Tristan Juricek <tjuricek@perforce.com> 1423602836 -0800 Committer: Tristan Juricek <tjuricek@perforce.com> 1423602836 -0800 sha1: c88642047f6560c7287e26113f5e1ce87e05ffdb push-state: complete parent-changes: 90ef9f83b0f53ac88223636c0ad653ab5b00e528=[1002716] |
||
#6 | 14716 | tjuricek |
2014.2.0.pre5 - Clearing the charset (calling ClientApi::SetTrans(0)) if the charset property is nil or none during construction. Changed README to use the correct incantation of --with-p4api-dir. Additionally, fixed an issue using that option in lieu of the ftp.perforce.com download. Also, removing any embedded distribution of the p4api. RubyGems sets a strict file size limit, which means we won't be able to distribute the C++ API embedded through their site. Imported from Git Author: Tristan Juricek <tjuricek@perforce.com> 1423518911 -0800 Committer: Tristan Juricek <tjuricek@perforce.com> 1423518911 -0800 sha1: 90ef9f83b0f53ac88223636c0ad653ab5b00e528 push-state: complete parent-changes: d10c4cae76976e7ca616cf17e116c9a16994236a=[999733] |
||
#5 | 14712 | tjuricek |
Configure 2014.2.0.pre4 label and update README instructions. Imported from Git Author: Tristan Juricek <tjuricek@perforce.com> 1423005443 -0800 Committer: Tristan Juricek <tjuricek@perforce.com> 1423005443 -0800 sha1: 196d731e2c17fe8cebd15057052718dc53ac58d6 push-state: complete parent-changes: f7591d8f78483b9872504cc77e1e193b3fae7419=[998345] |
||
#4 | 14692 | tjuricek |
Update spec maps to 14.2 definitions. This is the start of work for 2014.2.0.pre3. P4RUBY-168 Imported from Git Author: Tristan Juricek <tjuricek@perforce.com> 1418326946 -0800 Committer: Tristan Juricek <tjuricek@perforce.com> 1418327031 -0800 sha1: e609513caf80a760161fc1e65c134a93915fbb7f push-state: incomplete parent-changes: 1e000b52aae146751cd81ec1416e598f37c39149=[973742] |
||
#3 | 14690 | tjuricek |
Set passive=true before logging in to fix gem install problems in Docker environments. P4RUBY-171 Imported from Git Author: Tristan Juricek <tjuricek@perforce.com> 1417551368 -0800 Committer: Tristan Juricek <tjuricek@perforce.com> 1417551368 -0800 sha1: 07b676b152f0d146267480f3a9dff06603e0fe02 push-state: complete parent-changes: 46add71916859f2196e5af191be8ddd837dd5c4a=[964737] |
||
#2 | 14683 | tjuricek |
2014.2.0.pre1 Reorganization to support ruby Gem builds. The gem may not be immediately available since the rubygems.org credentials seem to be lost due to a hardware failure. In the meantime, this source should be testable against Linux and OS X. Precompiled builds will not be made available until Windows can be supported, which requires MinGW-w64 builds. (Note: this is a *fork* of MinGW, and not the same project, our MinGW builds are incompatible.) Once available it should be relatively straightfoward to use the rake-compile system to create crosscompiled builds for Windows, OS X, and Linux on the same build machine. Most tasks should be completed via rake in the future. There may be remnants of the old build system in here, no longer in use. Imported from Git Author: Tristan Juricek <tjuricek@perforce.com> 1415835954 -0800 Committer: Tristan Juricek <tjuricek@perforce.com> 1415836357 -0800 sha1: ad052c71a568ef12165e143a6866ad9ceffbb4a1 push-state: complete parent-branch: None@960958 parent-changes: 005052ae424bd69f426f7209e741ca1c8c3253c7=[960958] |
||
#1 | 14682 | Git Fusion |
Git Fusion branch management Imported from Git ghost-of-change-num: 960958 ghost-of-sha1: 005052ae424bd69f426f7209e741ca1c8c3253c7 ghost-precedes-sha1: ad052c71a568ef12165e143a6866ad9ceffbb4a1 parent-branch: None@960958 push-state: incomplete |