From: Eduardo Souza <eduardo@acts246.com>
To: Ruby developers <ruby-core@ruby-lang.org>
Subject: [ruby-core:81941] Re: [Ruby trunk Feature#12733] Bundle bundler to ruby core
Date: Thu, 6 Jul 2017 16:21:57 -0400 [thread overview]
Message-ID: <CANOHnbEwVRyZTvhcqpY427kQBR3oVRvrwaB+Xike2My8sSup=g@mail.gmail.com> (raw)
In-Reply-To: <redmine.journal-65660.20170706184940.e0e6e59f6076a284@ruby-lang.org>
[-- Attachment #1.1: Type: text/plain, Size: 2449 bytes --]
unsubscribe
On Thu, Jul 6, 2017 at 2:49 PM, <eregontp@gmail.com> wrote:
> Issue #12733 has been updated by Eregon (Benoit Daloze).
>
>
> hsbt (Hiroshi SHIBATA) wrote:
> > We can choose some strategy.
> >
> > * Rewrite bundler's rspec to minitest/spec
> > * Ruby core bundle rspec and integrate rspec and test suite of ruby core.
> > * Prepare isolation environment for bundler and rspec without test suite
> of ruby core. We add new test task named "make test-bundler` and iinvoke it
> on rubyci.
> > * etc...
> >
> > These are only technical side problem.
> >
> > I'm going to solve this problem used `isolation environment` as first.
>
>
> I think isolation environment is the best strategy (or the only
> reasonable).
>
> Rewriting tests is not an option for upstream development and is very
> time-consuming/error-prone (minitest/spec is a tiny subset of RSpec).
>
> I am not sure what you mean by bundling rspec, but rspec should not be
> available to normal Ruby users like default gems.
> It's a private dependency needed to run tests, and it probably makes most
> sense to install it as a gem when running the tests.
>
> I suspect it might also be difficult to run the tests in-tree.
> In that case I think it makes sense to require an installed Ruby to run
> more integration-like tests.
>
> ----------------------------------------
> Feature #12733: Bundle bundler to ruby core
> https://bugs.ruby-lang.org/issues/12733#change-65660
>
> * Author: hsbt (Hiroshi SHIBATA)
> * Status: Assigned
> * Priority: Normal
> * Assignee: hsbt (Hiroshi SHIBATA)
> * Target version: 2.5
> ----------------------------------------
> rubygems team has plan to migrate bundler into rubygems at rubygems 3.0.
>
> ref. https://github.com/rubygems/rubygems/issues/1681
>
> In current status, rubygems only use `Bundler` module on test suites.
> But we should track rubygems upstream step by step. I propose to bundle
> bundler
> for stdlib as default gem on ruby core repository.
>
> but we have some consideration. such as
>
> * bundler uses rspec for test suites. How to use rspec on ruby core
> repository?
> * Who are maintain bundler on ruby core repository?
>
> This issue is epic topic. Please comment your concerns or idea.
>
>
>
> --
> https://bugs.ruby-lang.org/
>
> Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
>
--
Eduardo Souza
www.acts246.com
[-- Attachment #1.2: Type: text/html, Size: 3741 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
next prev parent reply other threads:[~2017-07-06 20:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-12733.20160907060543@ruby-lang.org>
2016-09-07 6:05 ` [ruby-core:77172] [Ruby trunk Feature#12733] Bundle bundler to ruby core hsbt
2016-09-07 7:28 ` [ruby-core:77184] " eregontp
2016-09-09 16:48 ` [ruby-core:77231] " v.ondruch
2016-09-12 5:13 ` [ruby-core:77246] " duerst
2017-01-19 2:27 ` [ruby-core:79127] [Ruby trunk Feature#12733][Assigned] " hsbt
2017-03-13 5:46 ` [ruby-core:80100] [Ruby trunk Feature#12733] " hsbt
2017-06-22 1:18 ` [ruby-core:81737] " mail
2017-07-06 8:59 ` [ruby-core:81925] " hsbt
2017-07-06 18:49 ` [ruby-core:81936] " eregontp
2017-07-06 20:21 ` Eduardo Souza [this message]
2017-07-09 14:00 ` [ruby-core:81974] " v.ondruch
2017-07-11 3:34 ` [ruby-core:81996] " hsbt
2017-07-19 21:27 ` [ruby-core:82109] " mail
2017-07-27 5:11 ` [ruby-core:82190] " hsbt
2017-08-16 2:55 ` [ruby-core:82395] " shevegen
2017-08-31 7:19 ` [ruby-core:82567] " matz
2017-09-06 2:37 ` [ruby-core:82664] " hsbt
2017-09-06 4:39 ` [ruby-core:82666] " v.ondruch
2017-09-06 5:00 ` [ruby-core:82667] " shyouhei
2017-12-23 0:35 ` [ruby-core:84409] [Ruby trunk Feature#12733][Assigned] " hsbt
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANOHnbEwVRyZTvhcqpY427kQBR3oVRvrwaB+Xike2My8sSup=g@mail.gmail.com' \
--to=ruby-core@ruby-lang.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).