X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; q=dns; s=default; b=qnRqnuD qrzjMnLImdx6NylSYzTdcc+HI+PdwTnI7Qkly5YBfAJN8GD58M5qllMxr14+hxwe w6haI6o7O34IHCqgJDP4H8wbGyBcPL2DxjIvpidv++vB+fXUpLPQ8n6jfX/RxHmA 1uEZiiTFbYQbW6XBfbuAWwEqNFpbJIM6qrUo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; s=default; bh=DmV4UWZz4qCYj Int7DBMWJvJm5s=; b=Q5zA0dgoM8V8t0h7B9qchTls8+KMQ99IeMVOpzjEYS8Ts N0f7DIUO3iN44il4l9UjjxO7BO+oGNEtejiBdRODldnBQUtP/eCVC6Txh7SolLM4 GM6F8F9UEHk9J6Ma6ee6KksEGlFjrhPPZSoSFC5fI6bu7+Luryb0RK1qRszDjY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=HX-Envelope-From:sk:daniel., dan, HX-HELO:sk:mail-pl, H*r:sk:mail-pl X-HELO: mail-pl1-f179.google.com MIME-Version: 1.0 References: <1542703281 DOT 966819 DOT 1582906744 DOT 4CEC6D48 AT webmail DOT messagingengine DOT com> <1542728354 DOT 1862120 DOT 1583295232 DOT 4B1A5F52 AT webmail DOT messagingengine DOT com> In-Reply-To: From: Dan Kegel Date: Tue, 20 Nov 2018 09:00:40 -0800 Message-ID: Subject: Re: Bug: No json support anymore in Ruby 2.3.6 To: cygwin AT cygwin DOT com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes Hey all, looking at http://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.ini I see that there is a ruby-json package: @ ruby-json sdesc: "Ruby JSON module" ... but ruby does not currently depend on ruby-json: @ ruby sdesc: "Interpreted object-oriented scripting language" ... requires: cygwin libcrypt0 libdb5.3 libffi6 libgcc1 libgdbm4 libgmp10 libopenssl100 libreadline7 libssp0 libyaml0_2 ruby-did_you_mean ruby-psych ruby-rdoc rubygems zlib0 ... depends2: cygwin, libcrypt0, libdb5.3, libffi6, libgcc1, libgdbm4, libgmp10, libopenssl100, libreadline7, ruby-did_you_mean, ruby-psych, ruby-rdoc, rubygems, zlib0 Maybe rubygems should, let's see: @ rubygems sdesc: "Ruby module management system" ldesc: "A centralized Ruby extension management system, similar to Perl's CPAN" category: Ruby requires: ca-certificates ruby ruby-builder ruby-io-console ruby-minitest ruby-minitest4 ruby-psych ruby-rake ruby-rdoc ... depends2: ca-certificates, ruby, ruby-builder, ruby-io-console, ruby-minitest, ruby-psych, ruby-rake, ruby-rdoc I am not a cygwin developer, but it does kind of sound like the rubygems package might want to depend on the packages required to provide the 'default' gems from stdgems.org. The right way to phrase that request would be as a patch :-) if a cygwin ruby user who needs it has the time and energy to get into cygwin development. - Dan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple