all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Jack Hill <jackhill@jackhill.us>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Bundler 2
Date: Tue, 12 May 2020 18:00:52 -0500	[thread overview]
Message-ID: <20200512230052.sdcojmqnrkuzymov@thebird.nl> (raw)
In-Reply-To: <alpine.DEB.2.20.2005121743100.5735@marsh.hcoop.net>

On Tue, May 12, 2020 at 05:48:12PM -0400, Jack Hill wrote:
> On Tue, 12 May 2020, Josh Holland wrote:
> 
> > Indeed I see that gnu/packages/ruby.scm only packages Bundler v1.17.3,
> > though Bundler 2 was released in January 2019 [0].  I'm not hugely
> > familiar with the Ruby ecosystem, but reading the release announcement
> > suggests that they expect users/developers to have both Bundler 1 and
> > Bundler 2 available.  If I hadn't seen this, I'd have gone ahead and
> > submitted a patch simply upgrading the Bundler package definition, but
> > I'm not sure if that will then immediately break every package depending
> > on it that expects Bundler 1.
> > 
> > Is this a valid concern?  Should Guix provide packages for both Bundler
> > 1 and Bundler 2, or would just Bundler 2 be sufficient?  I'll still
> > write a definition for the new version, but I'll hold off submitting a
> > patch until I've had some feedback.
> > 
> > [0]: https://bundler.io/blog/2019/01/03/announcing-bundler-2.html
> 
> Josh,
> 
> Thanks for raising this question.
> 
> I'm not a Rubist, but we do wrangle some Ruby code at work (unfortunately,
> not yet with Guix). Our experience has been that everyone interacting with
> the code should use the same Bundler version, so I think that as long as
> Bundler v1 is supportable, we should provide both in Guix.
> 
> What do others think?

Bundler is a packaging tool that typically works at the source tree
level. Its approach is to pull all dependencies in. With Guix we don't
have much use for it. Better to package gems in Guix and benefit from
a true reproducible and dependable deployment system that *includes*
underlying dependencies, such as libxml and all that.

Sometimes it is useful to try gems.  I did write up in the past how I
mix Guix packages with Ruby gems.  Using bundler is just another
layer. See

https://gitlab.com/pjotrp/guix-notes/-/blob/master/RUBY.org#gnu-guix-ruby-with-bundler

Not much love for bundler therefore ;)

Pj.


  reply	other threads:[~2020-05-12 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 13:09 Bundler 2 Josh Holland
2020-05-12 21:48 ` Jack Hill
2020-05-12 23:00   ` Pjotr Prins [this message]
2020-05-14  7:34 ` Christopher Baines

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200512230052.sdcojmqnrkuzymov@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=jackhill@jackhill.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.