Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.ruby > #2107 > unrolled thread

Re: [ANN] hoe 2.9.2 Released

Back to article view | Back to comp.lang.ruby

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [ANN] hoe 2.9.2 Released Vassilis Rizopoulos <eldestdamphyr@gmail.com> - 2011-04-01 08:18 -0500
    Re: [ANN] hoe 2.9.2 Released Ryan Davis <ryand-ruby@zenspider.com> - 2011-04-01 16:12 -0500
      Re: [ANN] hoe 2.9.2 Released Vassilis Rizopoulos <eldestdamphyr@gmail.com> - 2011-04-02 01:28 -0500

#2107 — Re: [ANN] hoe 2.9.2 Released

Excellent work as always Ryan.
One thing:
rake package (and by extension rake install_gem, rake release) does not 
respect the Manifest.txt when it comes to the test/ directory.
All test_* files are included in the gem wether or not they are 
specified in Manifest.txt

This is a bit counterintuitive. It might be my personal way, but I have 
a bunch of tests for functionality that I do not yet want in the gem. 
This kinda throws a wrench in the works.
Cheers,
V.-
On 01/04/11 02:36 , Ryan Davis wrote:
> hoe version 2.9.2 has been released!
>
> *<http://rubyforge.org/projects/seattlerb/>
> *<http://seattlerb.rubyforge.org/hoe/>
> *<http://seattlerb.rubyforge.org/hoe/Hoe.pdf>
> *<http://github.com/jbarnette/hoe-plugin-examples>
>
> Hoe is a rake/rubygems helper for project Rakefiles. It helps you
> manage and maintain, and release your project and includes a dynamic
> plug-in system allowing for easy extensibility. Hoe ships with
> plug-ins for all your usual project tasks including rdoc generation,
> testing, packaging, and deployment.
>
> See class rdoc for help. Hint: `ri Hoe` or any of the plugins listed
> below.
>
> For extra goodness, see: http://seattlerb.rubyforge.org/hoe/Hoe.pdf
>
> Changes:
>
> ### 2.9.2 / 2011-03-31
>
> * 7 minor enhancements:
>
>    * Added :none as a testlib option to let you do whatever you want. (phiggins)
>    * Added Hoe#dependency(name, version, type = :runtime) for cleaner hoe specs.
>    * Added NOSUDO option to `rake gem_install`. (nihildeb)
>    * Include Rake::DSL to support future versions of rake
>    * Multiruby now skips mri_trunk if multiruby_skip includes 1.9
>    * Test#make_test_cmd now sorts test files (mostly for testing)
>    * Try using psych before syck.
>
> * 3 bug fixes:
>
>    * Clean generated extension library too
>    * Fixed a bug with sow -d or -t
>    * Fixed plugin activation via ~/.hoerc. (ged)
>
>


-- 
http://www.ampelofilosofies.gr

[toc] | [next] | [standalone]

#2129

On Apr 1, 2011, at 06:18 , Vassilis Rizopoulos wrote:

> Excellent work as always Ryan.
> One thing:
> rake package (and by extension rake install_gem, rake release) does not respect the Manifest.txt when it comes to the test/ directory.
> All test_* files are included in the gem wether or not they are specified in Manifest.txt
> 
> This is a bit counterintuitive. It might be my personal way, but I have a bunch of tests for functionality that I do not yet want in the gem. This kinda throws a wrench in the works.

Huh. I'd never seen that before, nor thought about it. That's really not a use-case I want to support. Good projects include their tests so users have access to them and that is encouraged by Hoe (although, admittedly, inadvertently on Hoe's part).

Why do you want to exclude some of your tests?

[toc] | [prev] | [next] | [standalone]

#2147

On 02/04/11 24:12 , Ryan Davis wrote:
> On Apr 1, 2011, at 06:18 , Vassilis Rizopoulos wrote:
>
>> Excellent work as always Ryan.
>> One thing:
>> rake package (and by extension rake install_gem, rake release) does not respect the Manifest.txt when it comes to the test/ directory.
>> All test_* files are included in the gem wether or not they are specified in Manifest.txt
>>
>> This is a bit counterintuitive. It might be my personal way, but I have a bunch of tests for functionality that I do not yet want in the gem. This kinda throws a wrench in the works.
> Huh. I'd never seen that before, nor thought about it. That's really not a use-case I want to support. Good projects include their tests so users have access to them and that is encouraged by Hoe (although, admittedly, inadvertently on Hoe's part).
>
> Why do you want to exclude some of your tests?
Well, the same way I want to exclude some of the files from the library 
: they're not ready for release yet.
If I don't release some of the features I'm working on then I don't want 
the accompanying tests in the gem as well.
The explicit manifest gives me that choice and as you well know someone 
will find a use case you haven't thought about :)

The thing is, this behaviour is inconsistent with the idea of the 
manifest, where you explicitly define what goes in the gem and what 
not.  I get to choose which files belong to the library but not which tests?

I mean, I can rename those tests to something other than test_* and they 
will be left out, but that also means that 'rake test' won't work for 
developing these tests while the funtionality they support is not released.

What bothers me the most is the deviation from the 'no surprises' path: 
Hoe explicitly supports the Manifest idea but breaks it for test/test_* 
files. From my point of view, it has to be consistent or documented with 
bold letters.

 From the Hoe.pdf, under the heading Manifest.txt
"Every project should know what it is shipping. This is done via an 
explicit list of everything that goes out in a release. Hoe uses this 
during packaging so that nothing embarrassing is picked up."

Thing is I never would have picked this up if I wasn't preparing the gem 
for GemTesters, so bonus points to GemTesters.

Cheers,
V.-

-- 
http://www.ampelofilosofies.gr

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.ruby

csiph-web