Thanks for clarifying! On Thu, Jul 11, 2019 at 1:34 PM Pavel Valena <pvalena@xxxxxxxxxx> wrote: > > ----- Original Message ----- > > From: "Vít Ondruch" <vondruch@xxxxxxxxxx> > > To: devel@xxxxxxxxxxxxxxxxxxxxxxx > > Sent: Thursday, July 11, 2019 8:45:12 AM > > Subject: Re: Fedora 31 Self-Contained Change proposal: Bundler 2.0 > > > > > > > > I think that we will end-up with this slightly edited version of the proposal > > :) > > > > > Keep Bundler 1.16 as rubygem-bundler1 subpackage of ruby package. > > > > The problem is that Ruby ships with bundled Bundler 1.x and RubyGems depends > > Bundler 1.x. Although I'm not sure how tight the coupling is :/ Upstream > > acts as the RubyGems and Bundler are inseparable, but I believe that the > > coupling is useful just for some niche use case. > > > > > > So the proposal is to move the independent rubygem-bundler into Bundler 2.x > > and replace the rubygem-bundler subpackage of ruby package by > > rubygem-bundler1 subpackage and keep it around as long as RubyGems does not > > migrate to the new version. > > > > Also, if I am not mistaken, the Gemfile.lock created by Bundler can enforce > > the version of Bundler required. > > > > > > Please note that it should be safe to install rubygem-bundler1 alongside the > > rubygem-bundler. > > The applications created (=Bundled) with Bundler 1 will still need to use Bundler 1 or they need to upgrade manually to Bundler 2[0]. > > Bundler 2 can dynamically select required runtime (v1 or v2) depending on the lock (=dependency) file. > > Regards, > Pavel > > [0] https://bundler.io/v2.0/guides/bundler_2_upgrade.html#upgrading-applications-from-bundler-1-to-bundler-2 > > > > > > > > > > > > > Vít > > > > > > > > Dne 10. 07. 19 v 20:49 Igor Gnatenko napsal(a): > > > > > > > > Why do we want to keep old version around? > > > > On Wed, Jul 10, 2019, 20:12 Ben Cotton < bcotton@xxxxxxxxxx > wrote: > > > > > > https://fedoraproject.org/wiki/Changes/Bundler_2.0 > > > > == Summary == > > Upgrade to Bundler 2.0, the latest stable gem version. > > > > == Owner == > > * Name: [[User:pvalena | Pavel Valena]], [[User:vondruch | Vit Ondruch]] > > * Email: pvalena@xxxxxxxxxx , vondruch@xxxxxxxxxx > > > > == Detailed Description == > > Bundler 2 is new major upstream release, that includes many > > improvements and bug fixes. > > > > == Benefit to Fedora == > > Keeping with a latest release, Bundler is enabling simple Ruby > > application dependency managemenent. > > > > == Scope == > > * Proposal owners: > > ** Move Bundler 1.16 to rubygem-bundler1 (sub)package. > > ** Build Bundler 2.0. Current changes: > > https://src.fedoraproject.org/rpms/rubygem-bundler/pull-request/5 > > ** Work has been done in a Copr repository: > > https://copr.fedorainfracloud.org/coprs/pvalena/rubygem-bundler/ > > * Other developers: N/A > > * Release engineering: N/A > > * Policies and guidelines: N/A > > * Trademark approval: N/A > > > > == Upgrade/compatibility impact == > > All applications and Gemfiles that currently work with Bundler 1 will > > continue to work with Bundler 2. > > > > Notable changes: > > * Dropped support for end of lifed Ruby versions 1.8.7 through 2.2 > > * Dropped support for end of lifed RubyGems versions 1.3.6 through 2.5 > > * Moved error messages from STDOUT to STDERR > > > > == How To Test == > > * No special hardware is needed. > > * Install Bundler 2 > > * Run `bundle --version` > > * Create new applications as before > > * If something doesn't work as it should, let us know. > > > > == User Experience == > > New features that come with Bundler 2.0 will be available. Current > > version will be available as rubygem-bundler1. > > > > == Documentation == > > https://bundler.io/docs.html > > > > == Release Notes == > > * https://bundler.io/blog/2019/01/03/announcing-bundler-2.html > > * https://bundler.io/blog/2018/11/04/an-update-on-bundler-2.html > > > > -- > > Ben Cotton > > He / Him / His > > Fedora Program Manager > > Red Hat > > TZ=America/Indiana/Indianapolis > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
