tetra 2.0.3 → 2.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: fc70e50e797a6d7f3e1f8bf939fcbd31e3fd355c
4
- data.tar.gz: 0ba9f1dfd08c8b427d77240e90de8333fde643a4
3
+ metadata.gz: f1e5c1456138783ecb6759fa94e795e71c1b4bba
4
+ data.tar.gz: c1a71c4a9802d350a7f08036a80d657b78675154
5
5
  SHA512:
6
- metadata.gz: dbe3806d2e52a522dbaa2edc2b0a2fdc62dfd44c5309c6a325c466a595d76ccd6219e863a3d257defc386c8393a3a50853a35c45a43a8583825c3d737955505f
7
- data.tar.gz: fa0973157b6f75ada34c98872dbf4d589dad18ca0cf89c8979dca8f59a2ee79cd3622f38b072b0b4986dd3d1bc701ba663999b135dec2cae0ac4466bd155cc1f
6
+ metadata.gz: b7c299c35196d1bed384db460b9fae82984de1cee142fd6643d762c4184a5f566ed2e5d8827ba5d1eb3f5c06d7c02cac7fc8075f0f424a44cae3667a7163b437
7
+ data.tar.gz: 6a9ff3327df7db1e85dc14156acaef6588ecd19f8ad2791aa333b933a5aa44e7db1e3b66fb7284bd45994b9404dd3884230b5df44936a163c23a6db9c84f1290
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- tetra (1.2.2)
4
+ tetra (2.0.3)
5
5
  clamp
6
6
  json_pure
7
7
  open4
@@ -18,7 +18,7 @@ GEM
18
18
  builder (3.2.2)
19
19
  childprocess (0.5.6)
20
20
  ffi (~> 1.0, >= 1.0.11)
21
- clamp (1.0.0)
21
+ clamp (1.1.2)
22
22
  cucumber (2.0.0)
23
23
  builder (>= 2.1.2)
24
24
  cucumber-core (~> 1.1.3)
@@ -32,7 +32,7 @@ GEM
32
32
  ffi (1.9.8)
33
33
  gherkin (2.12.2)
34
34
  multi_json (~> 1.3)
35
- json_pure (1.8.2)
35
+ json_pure (2.1.0)
36
36
  multi_json (1.11.0)
37
37
  multi_test (0.1.2)
38
38
  open4 (1.3.4)
@@ -50,7 +50,7 @@ GEM
50
50
  diff-lcs (>= 1.2.0, < 2.0)
51
51
  rspec-support (~> 3.2.0)
52
52
  rspec-support (3.2.2)
53
- rubyzip (1.1.7)
53
+ rubyzip (1.2.1)
54
54
  text (1.3.1)
55
55
 
56
56
  PLATFORMS
@@ -61,3 +61,6 @@ DEPENDENCIES
61
61
  rake
62
62
  rspec
63
63
  tetra!
64
+
65
+ BUNDLED WITH
66
+ 1.12.5
data/README.md CHANGED
@@ -11,7 +11,7 @@ See [MOTIVATION.md](MOTIVATION.md) for further information.
11
11
  You need:
12
12
 
13
13
  * [Ruby 1.9.2](https://www.ruby-lang.org/en/) or later;
14
- * [git](http://git-scm.com/);
14
+ * [git](http://git-scm.com/) with your credentials set in ~/.gitconfig (name and email)
15
15
  * some basic Unix commands: bash, unzip, tar;
16
16
  * a JDK that can compile whatever software you need to package;
17
17
  * Fedora only: packages to compile native gems, use `yum install ruby-devel gcc-c++ zlib-devel`;
@@ -25,9 +25,10 @@ Install `tetra` via RubyGems:
25
25
  Building a package with `tetra` is quite unusual — this is a deliberate choice, so don't worry. Basic steps are:
26
26
 
27
27
  * `tetra init <package name> package_sources.tar.gz` to initialize the project and unpack original sources;
28
+ * `cd` into the newly created `<package name>` directory
28
29
  * if anything other than `ant` and `mvn` is needed in order to build the project, add it to the `kit/` directory in binary form;
29
30
  * execute `tetra dry-run`, which will open a bash subshell. Build your project, and when you are done conclude by exiting the subshell with `Ctrl+D`;
30
- * execute `tetra generate-all`: tetra will scaffold spec files and tarballs.
31
+ * `cd` into the directory that contains `pom.xml` and execute `tetra generate-all`: tetra will scaffold spec files and tarballs.
31
32
 
32
33
  Done!
33
34
 
@@ -113,14 +113,14 @@ Instructions:
113
113
 
114
114
  Assuming your project uses the [Gradle Wrapper](http://gradle.org/docs/current/userguide/gradle_wrapper.html);
115
115
 
116
- * during your dry-run build, add the `--gradle-user-home /tmp/gradle --project-cache-dir /tmp/gradle-project` commandline options to `gradlew` in order to download files in the `/tmp` directory instead of your home. Typically:
116
+ * during your dry-run build, add the `--gradle-user-home /tmp/gradle --project-cache-dir /tmp/gradle-project` commandline options to `gradlew` in order to download gradle files in the `/tmp` directory instead of your home. Typically:
117
117
  ```
118
118
  ./gradlew --gradle-user-home /tmp/gradle --project-cache-dir /tmp/gradle-project clean build -x test
119
119
  ```
120
- Note that gradle 1.6 has a bug and it will not honor the `--gradle-user-home` flag. Use instead:
120
+ Note that gradle 1.6 has a bug and it will not honor the `--gradle-user-home` flag. Even if you use a fixed gradle, an old gradlew could not honor it. Use instead:
121
121
  ```
122
122
  export GRADLE_USER_HOME=/tmp/gradle
123
- ./gradlew --project-cache-dir /tmp/gradle-project --offline clean build -x test
123
+ ./gradlew --project-cache-dir /tmp/gradle-project clean build -x test
124
124
  ```
125
125
 
126
126
  * after the build has finished but prior ending the dry-run, copy all files to your kit with:
@@ -128,7 +128,12 @@ Assuming your project uses the [Gradle Wrapper](http://gradle.org/docs/current/u
128
128
  cp -r /tmp/gradle* ../../kit/
129
129
  ```
130
130
 
131
- * after your build script is generated, add the following line to `build.sh` in order to restore files from `kit/` to `/tmp` before `gradlew` is called:
131
+ * after your build script is generated, remove from `build.sh` the following line:
132
+ ```
133
+ cp -r /tmp/gradle* ../../kit/
134
+ ```
135
+
136
+ * Then add the following line to `build.sh` in order to restore files from `kit/` to `/tmp` before `gradlew` is called:
132
137
  ```
133
138
  cp -r kit/* /tmp
134
139
  ```
@@ -139,6 +144,8 @@ Note that you cannot put files in `kit/` directly because your build would break
139
144
 
140
145
  Also note that Gradle typically ships with libnative as a platform-dependent binary library. That means you will need to build the RPM package on an x86_64 host.
141
146
 
147
+ Finally note that if you want to upgrade gradle and remove the previous versions, you should remove /tmp/gradle* directories, as well as the kit/gradle* directories (use git rm for this). Of course remember to adjust your gradlew call, build.gradle and/or gradle-wrapper.properties files with the new version.
148
+
142
149
  ## [OBS](build.opensuse.org) integration
143
150
 
144
151
  If you want to submit your package to OBS, you can do so by copying contents of the `packages` in a proper OBS project directory.
@@ -1,7 +1,7 @@
1
1
  # encoding: UTF-8
2
2
 
3
3
  module Tetra
4
- # encapsulates unzip
4
+ # encapsulates tar
5
5
  class Tar
6
6
  include ProcessRunner
7
7
 
@@ -2,5 +2,5 @@
2
2
 
3
3
  # base module for tetra
4
4
  module Tetra
5
- VERSION = "2.0.3"
5
+ VERSION = "2.0.4"
6
6
  end
@@ -80,7 +80,7 @@ describe "`tetra generate-all`", type: :aruba do
80
80
 
81
81
  # second dry-run, all normal
82
82
  cd(File.join("src", "commons-collections4-4.1-src"))
83
- @aruba_timeout_seconds = 120
83
+ @aruba_timeout_seconds = 240
84
84
  run_interactive("tetra dry-run")
85
85
  type("mvn package -DskipTests")
86
86
  type("\u{0004}") # ^D (Ctrl+D), terminates bash with exit status 0
@@ -15,7 +15,7 @@ describe "`tetra generate-spec`", type: :aruba do
15
15
  run_simple("tetra change-sources --no-archive")
16
16
  expect(output_from("tetra change-sources --no-archive")).to include("New sources committed")
17
17
 
18
- @aruba_timeout_seconds = 120
18
+ @aruba_timeout_seconds = 240
19
19
  run_interactive("tetra dry-run")
20
20
  type("mvn package -DskipTests")
21
21
  type("\u{0004}") # ^D (Ctrl+D), terminates bash with exit status 0
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: tetra
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.3
4
+ version: 2.0.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Silvio Moioli
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2017-09-20 00:00:00.000000000 Z
11
+ date: 2018-01-19 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: rake