Re: bundler and build-essential (was Fwd: Re: migrating to Debian gitlab)
* Antonio Terceiro <terceiro@debian.org> [160215 21:15]:
> On Mon, Feb 15, 2016 at 11:53:35PM +0530, Pirate Praveen wrote:
> >
> >
> >
> > -------- Original Message --------
> > From: Christian Seiler <christian@iwakd.de>
> > Sent: 2016, ഫെബ്രുവരി 15 10:05:08 PM IST
> > To: Pirate Praveen <praveen@onenetbeyond.org>, debian-devel@lists.debian.org
> > Subject: Re: migrating to Debian gitlab
> >
> > [... Skipped other discussion...]
> >
> > >> (Btw., off topic: I haven't done much with ruby, but gitlab pulls in
> > >> build-essential via gitlab Depends: bundler and bundler Recommends:
> > >> build-essential. While this is Recommends, so you can avoid it if
> > >> you want to, it still seems weird to me that build-essential is
> > >> pulled in by default implicitly via gitlab...)
>
> I think bundler does not _need_ to depend on build-essential, or
> ruby-dev.
Which is why it doesn't :-)
> I made the following changes to the packaging:
>
> Avoid installing toolchain on end user systems
> http://deb.li/rAQ7
>
> mention build-essential, ruby-dev and sudo for development
> http://deb.li/3I29d
>
> I plan to upload those, together with a new upstream version, during the
> weekend if nobody objects.
This breaks the "use bundler standalone" usecase. Given that noone
ever reads descriptions or documentation, please remove my name from
Uploaders: if you upload this.
Best,
--
,''`. Christian Hofstaedtler <zeha@debian.org>
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
Reply to: