newgem 0.9.1 → 0.9.2

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.
data/History.txt CHANGED
@@ -1,3 +1,10 @@
1
+ +++ 0.9.2 18/4/2007
2
+
3
+ + 1 minor improvement:
4
+ + Generated apps include a "require 'rubygems' line at the top"
5
+ + 1 website fix
6
+ + Notes that the index.txt file includes Dr Nic details, not their own.[FIXME!!]
7
+
1
8
  +++ 0.9.1 16/4/2007
2
9
 
3
10
  + 1 bugfix:
data/bin/newgem CHANGED
@@ -1,5 +1,11 @@
1
1
  #!/usr/bin/env ruby
2
2
 
3
+ begin
4
+ require 'rubygems'
5
+ rescue LoadError
6
+ # no rubygems to load, so we fail silently
7
+ end
8
+
3
9
  require 'fileutils'
4
10
  require 'active_support'
5
11
  require 'optparse'
@@ -2,7 +2,7 @@ module Newgem #:nodoc:
2
2
  module VERSION #:nodoc:
3
3
  MAJOR = 0
4
4
  MINOR = 9
5
- TINY = 1
5
+ TINY = 2
6
6
 
7
7
  STRING = [MAJOR, MINOR, TINY].join('.')
8
8
  end
data/templates/app.rb CHANGED
@@ -3,6 +3,12 @@
3
3
  # Created by MYNAME on #{(now = Time.now).year}-#{now.month}-#{now.day}.
4
4
  # Copyright (c) #{now.year}. All rights reserved.
5
5
 
6
+ begin
7
+ require 'rubygems'
8
+ rescue LoadError
9
+ # no rubygems to load, so we fail silently
10
+ end
11
+
6
12
  require 'optparse'
7
13
 
8
14
  # NOTE: the option -p/--path= is given as an example, and should probably be replaced in your application.
data/website/index.html CHANGED
@@ -247,6 +247,9 @@ NOW - update wizzo/Rakefile with gem description, etc
247
247
  <p>Remember, the Rakefile is yours to extend as you please with more rake tasks, such as the <code>website</code> tasks already added.</p>
248
248
 
249
249
 
250
+ <p>For more information about each task, see the <a href="http://seattlerb.rubyforge.org/hoe/">Hoe <span class="caps">README</span></a></p>
251
+
252
+
250
253
  <h2>Related articles</h2>
251
254
 
252
255
 
@@ -279,7 +282,7 @@ other stories and things.</p>
279
282
 
280
283
  <p>Comments are welcome. Send an email to <a href="mailto:drnicwilliams@gmail.com">Dr Nic Williams</a>.</p>
281
284
  <p class="coda">
282
- <a href="mailto:drnicwilliams@gmail.com">Dr Nic</a>, 15th April 2007<br>
285
+ <a href="mailto:drnicwilliams@gmail.com">Dr Nic</a>, 17th April 2007<br>
283
286
  Theme extended from <a href="http://rb2js.rubyforge.org/">Paul Battley</a>
284
287
  </p>
285
288
  </div>
data/website/index.txt CHANGED
@@ -72,6 +72,8 @@ The final step before releasing your gem to the world is the all-important websi
72
72
 
73
73
  Run the rake task <code>rake website_generate</code> to convert all your website txt files into html files.
74
74
 
75
+ NOTE: Currently, the initial <code>index.txt</code> file includes my details not yours. Currently you need to change this manually.
76
+
75
77
  If you don't want a website, remove the <code>website</code> related files from the Manifest.txt.
76
78
 
77
79
  Make sure you've generated the <code>website/index.html</code> file before continuing to package and release your gem (unless you remove it from the Manifest.txt).
@@ -160,6 +162,8 @@ See them all with:
160
162
 
161
163
  Remember, the Rakefile is yours to extend as you please with more rake tasks, such as the <code>website</code> tasks already added.
162
164
 
165
+ For more information about each task, see the "Hoe README":http://seattlerb.rubyforge.org/hoe/
166
+
163
167
  h2. Related articles
164
168
 
165
169
  * "Original blog article and tutorial":http://drnicwilliams.com/2006/10/11/generating-new-gems/
@@ -130,8 +130,138 @@ $ rubyforge names
130
130
 
131
131
 
132
132
  <p><a href="index.html#setup_rubyforge">Return to releasing your gem</a></p>
133
+
134
+
135
+ <h2>rubyforge docco</h2>
136
+
137
+
138
+ <p>The best rubyforge command documentation is available via the application itself (see below) and the <a href="http://codeforpeople.rubyforge.org/rubyforge/">RDocs</a></p>
139
+
140
+
141
+ <pre>$ rubyforge help
142
+ SYNOPSIS
143
+
144
+ rubyforge [options]* mode [mode_args]*
145
+
146
+ DESCRIPTION
147
+
148
+ simplistic script which automates a limited set of rubyforge operations
149
+
150
+ MODES
151
+
152
+ setup()
153
+ initializes your .rubyforge directory. you need to run this first before
154
+ doing anything else.
155
+
156
+ example :
157
+ rubyforge setup
158
+
159
+ config([project])
160
+ Helps you populate your auto-config.yml file by scraping rubyforge and
161
+ getting your groups, projects, and releases.
162
+
163
+ example :
164
+ rubyforge config
165
+ rubyforge config myproject
166
+
167
+ names()
168
+ Prints out the names of your configured groups and projects.
169
+
170
+ example :
171
+ rubyforge names
172
+
173
+ login()
174
+ sends username and password from config.yml (or --username/--password
175
+ options) and stores login cookie in cookie.dat. this is required for
176
+ subsquent operations work.
177
+
178
+ example :
179
+ rubyforge login
180
+ rubyforge login --username zaphod --password 42
181
+
182
+ create_package(group_id, package_name)
183
+ creates the named package under the specified group.
184
+
185
+ example :
186
+ rubyforge create_package 1024 traits
187
+ rubyforge login &#38;&#38; rubyforge create_package codeforpeople.com traits
188
+
189
+ add_release(group_id, package_id, release_name, userfile)
190
+ release a file as release_name under the specified group_id and
191
+ package_id.
192
+
193
+ example :
194
+ rubyforge add_release codeforpeople.com traits 0.8.0 traits-0.8.0.gem
195
+ rubyforge add_release codeforpeople.com traits 0.8.0 traits-0.8.0.tgz
196
+ rubyforge add_release 1024 1242 0.8.0 traits-0.8.0.gem
197
+ rubyforge login &#38;&#38; rubyforge add_release 1024 1242 0.8.0 traits-0.8.0.gem
198
+
199
+ add_file(group_id, package_id, release_id, userfile)
200
+ add a file to an existing release under the specified group_id,
201
+ package_id, and release_id
202
+
203
+ example :
204
+ rubyforge add_file codeforpeople.com traits 0.8.0 traits-0.8.0.gem
205
+ rubyforge add_file codeforpeople.com traits 0.8.0 traits-0.8.0.tgz
206
+ rubyforge add_file 1024 1242 0.8.0 traits-0.8.0.gem
207
+
208
+ delete_package(group_id, package_name)
209
+ deletes a package and all its files.
210
+
211
+ example :
212
+ rubyforge delete_package codeforpeople.com traits
213
+ rubyforge delete_package 1024 traits
214
+
215
+ NOTES
216
+
217
+ - In order to use group_id, package_id, or release_id by name,
218
+ rather than number, you must edit the rubyforge[group_ids] and
219
+ rubyforge[package_ids] translation tables in your config.yml. See
220
+ the config command for more information and help.
221
+
222
+ - don't forget to login! logging in will store a cookie in your
223
+ .rubyforge directory which expires after a time. always run the login
224
+ command before any operation that requires authentication, such as
225
+ uploading a package.
226
+
227
+ TODO
228
+
229
+ - add error checking. this requires screen scraping to see of an operation
230
+ succeeded since 200 is returned from rubyforge even for failed operations
231
+ and only the html text reveals the status.
232
+
233
+ OPTIONS
234
+
235
+ global :
236
+ --help , -h
237
+ this message
238
+ --config , -c
239
+ specify a config file (default /Users/nicwilliams/.rubyforge/user-config.yml)
240
+ --username , -u
241
+ specify username, taken from config otherwise
242
+ --password , -p
243
+ specify password, taken from config otherwise
244
+ --cookie_jar , -C
245
+ specify cookie storage file (default /Users/nicwilliams/.rubyforge/cookie.dat)
246
+
247
+ add_release :
248
+ --is_private , -P
249
+ if true, release is not public
250
+ --release_date , -r
251
+ specify time of release (default 'now')
252
+ --type_id , -t
253
+ specify filetype code (default determined by ext)
254
+ --processor_id , -o
255
+ specify processor (default 'Any')
256
+ --release_notes , -n
257
+ specify release notes as string or file
258
+ --release_changes , -a
259
+ specify release changes as string or file
260
+ --preformatted , -f
261
+ specify whether release_notes/changes are preformatted
262
+ </pre>
133
263
  <p class="coda">
134
- <a href="mailto:drnicwilliams@gmail.com">Dr Nic</a>, 13th April 2007<br>
264
+ <a href="mailto:drnicwilliams@gmail.com">Dr Nic</a>, 17th April 2007<br>
135
265
  Theme extended from <a href="http://rb2js.rubyforge.org/">Paul Battley</a>
136
266
  </p>
137
267
  </div>
@@ -69,4 +69,131 @@ Check that the new package has been successfully added to your local config file
69
69
 
70
70
  h2. You are now ready to release gems!
71
71
 
72
- "Return to releasing your gem":index.html#setup_rubyforge
72
+ "Return to releasing your gem":index.html#setup_rubyforge
73
+
74
+ h2. rubyforge docco
75
+
76
+ The best rubyforge command documentation is available via the application itself (see below) and the "RDocs":http://codeforpeople.rubyforge.org/rubyforge/
77
+
78
+ <pre>$ rubyforge help
79
+ SYNOPSIS
80
+
81
+ rubyforge [options]* mode [mode_args]*
82
+
83
+ DESCRIPTION
84
+
85
+ simplistic script which automates a limited set of rubyforge operations
86
+
87
+ MODES
88
+
89
+ setup()
90
+ initializes your .rubyforge directory. you need to run this first before
91
+ doing anything else.
92
+
93
+ example :
94
+ rubyforge setup
95
+
96
+ config([project])
97
+ Helps you populate your auto-config.yml file by scraping rubyforge and
98
+ getting your groups, projects, and releases.
99
+
100
+ example :
101
+ rubyforge config
102
+ rubyforge config myproject
103
+
104
+ names()
105
+ Prints out the names of your configured groups and projects.
106
+
107
+ example :
108
+ rubyforge names
109
+
110
+ login()
111
+ sends username and password from config.yml (or --username/--password
112
+ options) and stores login cookie in cookie.dat. this is required for
113
+ subsquent operations work.
114
+
115
+ example :
116
+ rubyforge login
117
+ rubyforge login --username zaphod --password 42
118
+
119
+ create_package(group_id, package_name)
120
+ creates the named package under the specified group.
121
+
122
+ example :
123
+ rubyforge create_package 1024 traits
124
+ rubyforge login && rubyforge create_package codeforpeople.com traits
125
+
126
+ add_release(group_id, package_id, release_name, userfile)
127
+ release a file as release_name under the specified group_id and
128
+ package_id.
129
+
130
+ example :
131
+ rubyforge add_release codeforpeople.com traits 0.8.0 traits-0.8.0.gem
132
+ rubyforge add_release codeforpeople.com traits 0.8.0 traits-0.8.0.tgz
133
+ rubyforge add_release 1024 1242 0.8.0 traits-0.8.0.gem
134
+ rubyforge login && rubyforge add_release 1024 1242 0.8.0 traits-0.8.0.gem
135
+
136
+ add_file(group_id, package_id, release_id, userfile)
137
+ add a file to an existing release under the specified group_id,
138
+ package_id, and release_id
139
+
140
+ example :
141
+ rubyforge add_file codeforpeople.com traits 0.8.0 traits-0.8.0.gem
142
+ rubyforge add_file codeforpeople.com traits 0.8.0 traits-0.8.0.tgz
143
+ rubyforge add_file 1024 1242 0.8.0 traits-0.8.0.gem
144
+
145
+ delete_package(group_id, package_name)
146
+ deletes a package and all its files.
147
+
148
+ example :
149
+ rubyforge delete_package codeforpeople.com traits
150
+ rubyforge delete_package 1024 traits
151
+
152
+ NOTES
153
+
154
+ - In order to use group_id, package_id, or release_id by name,
155
+ rather than number, you must edit the rubyforge[group_ids] and
156
+ rubyforge[package_ids] translation tables in your config.yml. See
157
+ the config command for more information and help.
158
+
159
+ - don't forget to login! logging in will store a cookie in your
160
+ .rubyforge directory which expires after a time. always run the login
161
+ command before any operation that requires authentication, such as
162
+ uploading a package.
163
+
164
+ TODO
165
+
166
+ - add error checking. this requires screen scraping to see of an operation
167
+ succeeded since 200 is returned from rubyforge even for failed operations
168
+ and only the html text reveals the status.
169
+
170
+ OPTIONS
171
+
172
+ global :
173
+ --help , -h
174
+ this message
175
+ --config , -c
176
+ specify a config file (default /Users/nicwilliams/.rubyforge/user-config.yml)
177
+ --username , -u
178
+ specify username, taken from config otherwise
179
+ --password , -p
180
+ specify password, taken from config otherwise
181
+ --cookie_jar , -C
182
+ specify cookie storage file (default /Users/nicwilliams/.rubyforge/cookie.dat)
183
+
184
+ add_release :
185
+ --is_private , -P
186
+ if true, release is not public
187
+ --release_date , -r
188
+ specify time of release (default 'now')
189
+ --type_id , -t
190
+ specify filetype code (default determined by ext)
191
+ --processor_id , -o
192
+ specify processor (default 'Any')
193
+ --release_notes , -n
194
+ specify release notes as string or file
195
+ --release_changes , -a
196
+ specify release changes as string or file
197
+ --preformatted , -f
198
+ specify whether release_notes/changes are preformatted
199
+ </pre>
metadata CHANGED
@@ -3,8 +3,8 @@ rubygems_version: 0.9.2
3
3
  specification_version: 1
4
4
  name: newgem
5
5
  version: !ruby/object:Gem::Version
6
- version: 0.9.1
7
- date: 2007-04-16 00:00:00 +02:00
6
+ version: 0.9.2
7
+ date: 2007-04-18 00:00:00 +02:00
8
8
  summary: Make your own gems at home
9
9
  require_paths:
10
10
  - lib