Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion "Local" group or group metadata for optional gems

Received: by 10.224.196.66 with SMTP id ef2mr248387qab.22.1305768309134;
        Wed, 18 May 2011 18:25:09 -0700 (PDT)
X-BeenThere: ruby-bundler@googlegroups.com
Received: by 10.224.175.74 with SMTP id w10ls159137qaz.0.gmail; Wed, 18 May
 2011 18:25:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.177.129 with SMTP id bi1mr283821qab.11.1305768308540; Wed,
 18 May 2011 18:25:08 -0700 (PDT)
Received: by cu4g2000vbb.googlegroups.com with HTTP; Wed, 18 May 2011 18:25:08
 -0700 (PDT)
Date: Wed, 18 May 2011 18:25:08 -0700 (PDT)
In-Reply-To: <BANLkTimDQOF+Fb4FK3K6vCx+UCB60+s0Qw@mail.gmail.com>
X-IP: 201.52.145.172
References: <52f0c9bc-441c-4e73-a9af-1923a47cd6cf@w36g2000vbi.googlegroups.com>
 <BANLkTik75HFGdzVGxrWCFunn7O1OT67tfg@mail.gmail.com> <47f1c198-ad42-450e-851d-025309f577b3@k27g2000pri.googlegroups.com>
 <BANLkTimDQOF+Fb4FK3K6vCx+UCB60+s0Qw@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_7; en-us)
 AppleWebKit/533.21.1 (KHTML, like Gecko) Version/5.0.5 Safari/533.21.1,gzip(gfe)
Message-ID: <95a54b7a-485d-4ba6-9104-e58f4ca440a5@cu4g2000vbb.googlegroups.com>
Subject: Re: "Local" group or group metadata for optional gems
From: =?ISO-8859-1?Q?Lucas_H=FAngaro?= <lucashung...@gmail.com>
To: ruby-bundler <ruby-bundler@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

That would be nice too.

On May 18, 5:55=A0pm, Christopher Small <metasoar...@gmail.com> wrote:
> What about something like
>
> =A0 =A0group :development do
> =A0 =A0 =A0gem "wirble", :optional =3D> true, :set =3D> "A"
> =A0 =A0 =A0gem "looksee", :optional =3D> true, :set =3D> "B"
> =A0 =A0 =A0gem "rspec-rails"
> =A0 =A0end
>
> so that you could do
>
> =A0 =A0bundle install --include-optional=3DB
>
> if you just wanted those in set B, but not in set A?
>
> Chris
>
> On Wed, May 18, 2011 at 1:23 PM, Lucas H=FAngaro <lucashung...@gmail.com>=
wrote:
>
>
>
> > Hmmm, maybe add an "optional" flag to each gem, so we don't mess with
> > groups:
>
> > =A0 =A0group :development do
> > =A0 =A0 =A0gem "wirble", :optional =3D> true
> > =A0 =A0 =A0gem "looksee", :optional =3D> true
> > =A0 =A0 =A0gem "rspec-rails"
> > =A0 =A0end
>
> > On May 18, 4:14 pm, Christopher Small <metasoar...@gmail.com> wrote:
> > > Seems like ideally you would want to have something more robust to al=
low
> > for
> > > multiple optional groups. That way, if some of the devs want to use g=
em A
> > > but not gem B and other developers want to use gem B but not gem A, t=
hat
> > > could be accomplished with optional A and a B groups. Maybe "group" i=
s
> > not
> > > the right name for these things, given that it already has meaning. M=
aybe
> > > "set" or something.
>
> > > Chris
>
> > > On Tue, May 17, 2011 at 8:45 PM, Lucas H=FAngaro <lucashung...@gmail.=
com
> > >wrote:
>
> > > > Hi there!
>
> > > > It's a common issue to have gems that one developer uses while work=
ing
> > > > on some app, but other developers in the team don't want to use.
> > > > Things like wirble, looksee and awesome_print comes to mind. It's t=
he
> > > > kind of thing you don't want to force other people to install since
> > > > it's not an application dependency, it's just a non-required
> > > > environment tool. So, putting those dependencies in the Gemfile is =
bad
> > > > but also required, as there's no way to use them otherwise (at leas=
t I
> > > > haven't see one yet).
>
> > > > To solve this I thought of two options:
>
> > > > 1. "Local" gems group, like:
> > > > =A0 =A0group :local do
> > > > =A0 =A0 =A0gem "wirble"
> > > > =A0 =A0 =A0gem "looksee"
> > > > =A0 =A0end
>
> > > > 2. Adding some metadata option to flag an optional gem:
> > > > =A0 =A0group :development, :optional =3D> true do
> > > > =A0 =A0 =A0gem "wirble"
> > > > =A0 =A0 =A0gem "looksee"
> > > > =A0 =A0end
>
> > > > Bundler then wouldn't complain if these gems aren't installed and t=
hey
> > > > would be installed only if a flag is provided, like:
>
> > > > $ bundler install --include-optional
>
> > > > Is this a good option?
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "ruby-bundler" group.
> > > > To post to this group, send email to ruby-bundler@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > ruby-bundler+unsubscribe@googlegroups.com.
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/ruby-bundler?hl=3Den.
>
> > --
> > You received this message because you are subscribed to the Google Grou=
ps
> > "ruby-bundler" group.
> > To post to this group, send email to ruby-bundler@googlegroups.com.
> > To unsubscribe from this group, send email to
> > ruby-bundler+unsubscribe@googlegroups.com.
> > For more options, visit this group at