cognitive dissonance with inconsistent usage of groups

[Chad Woolley]

Why does the CLI 'install' command only allow you to *exclude* groups
via --without, but the Bundler.setup and Bundler.require methods only
allow you to *include* groups. There is also the added caveat that the
methods observe anything that was excluded via --without, which for me
just confuses things further.

Is there some underlying fundamental reason behind this mismatch? If
not, it seems logical to support either inclusion or exclusion
wherever any of these functions reference groups (obviously failing
with a descriptive if you try to setup or require a group which has
not been installed).

Thanks,
-- Chad

[Ed Howland]

+1

Also, if you have multiple groups, such as a use case where
development, staging, production need specific gems or versions
thereof, you have to "exclude" 2 groups for a particular platform:

staging:
--without development, production

development:
-- without staging, prodcution

production:
--without staging, development

Confusing

There was talk at one time of the '--only' flag. Can we bring it back.?

Cheers,
Ed

Ed Howland
http://greenprogrammer.wordpress.com
http://twitter.com/ed_howland

> --
> You received this message because you are subscribed to the Google Groups "ruby-bundler" group.
> To post to this group, send email to ruby-b...@googlegroups.com.
> To unsubscribe from this group, send email to ruby-bundler...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ruby-bundler?hl=en.
>
>