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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=yPmJ3aXRY7YMWUZl sTZulCj/B0nJgPvtO2WfPV62XlkGqXK1weHcPM1kdBNC96OD4/omcBwHpkFs8tB6 5KTUPWqu0oOAOtZbz+NaevWTSjg4hbLOsufhYCdZJzG1bHC2KHgjRyANcPlgSf+I k/n4oLE8+qbku3Sr69uKbYrxxnk= 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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=eMarWYH7I3ZYXhfkmg8ISG JmnJk=; b=OKRcsnk3xz5ZW1at2BRvHV0ZwELDAP6RCyfvHwQNKk90h6LIbc51vv n8JS8+YVFExc0zvlA77HFHiaMSMeFITJFyZpCbiwcUv5YHy0FYVjeBHiQ64R12Rs TZZzyKhQ0ds7+Ng4jG84zN0a4WnDtdX4r904+Pxs9LFLLiMhrPvjQ= 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=-0.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=packaging, H*R:D*ca, Hey, dan X-HELO: smtp-out-so.shaw.ca Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: Bug: No json support anymore in Ruby 2.3.6 To: cygwin AT cygwin DOT com 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> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: Date: Tue, 20 Nov 2018 12:10:07 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 2018-11-20 10:00, Dan Kegel wrote: > 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" > ... > 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" > ... > 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. It's more a case of package.cygport tweaks by the ruby/library/-gems maintainer to define packages and dependencies to get all required packages installed. Dependencies are circular if gems depend on ruby, and ruby depends on the standard library gems: how that is handled in packaging must be decided by the maintainer, when they have time. It might require a bit of restructuring so that e.g. exes and libs are packaged as ruby-bin and ruby-lib, gems depend on bin and lib, and ruby only provides global files but depends on all the standard bits to get them installed. Like many developers I know enough about ruby to find and install packages I need to run the tools I *use* sometimes, and hack a bit, but little more; same for python, perl, .net, etc. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- 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