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:message-id:from:to:mime-version
	:content-transfer-encoding:content-type:subject:in-reply-to
	:references:date; q=dns; s=default; b=FTyvnuU2w24yFDyOrwbTiCKJsF
	WWHiTEz/xWeMqrKwgeBjRcfZSelreolHoF8/FQ92VR5w2j6w5covA3N3ZeJFf7hE
	GTjY8liFcozMVDKAMmP4LuS1qZzAOwSF+BP1nOWkfvrHmm8xiEh+a5RSmDubfx8G
	RVZs4js3mWGNYgdes=
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:message-id:from:to:mime-version
	:content-transfer-encoding:content-type:subject:in-reply-to
	:references:date; s=default; bh=PU5oprmTNy1IuiwJxuBGk5Ntj7I=; b=
	u4RPZpcR9LUyr/yHJL2i1rRf6VJge4rzDWAdl+il3b5LnDgWRj4I5g/7VDPduOs8
	AHCE/W7oK3qXjo981c2ziXOVeDXMYfO+T8f12ema7OucRN/j1SjFNa8e8SCo01sV
	QvmNt8/V7ajCwzdzjPtqEFxWMzyC8mKwp3s7xsGMANI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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.6 required=5.0 tests=AWL,BAYES_00,BODY_8BITS,FREEMAIL_FROM,GARBLED_BODY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=F, packaging, posting, sites
X-HELO:	new4-smtp.messagingengine.com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=mm.st; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:in-reply-to:references:date; s=fm2; bh=FSo yRJfr4dk657+oUz8D/VvFwSND+Zs5brdufey1NxM=; b=BDPonCrJoQgR/h8ce8B J5WoBMDiFZcbc5Gz1ACGENJKX6pKT3Vk29xoYbTXqVTLxZVMWhN6cmtQ6ITXFphD HIHe00kUDyiuKZil0tyGTjR4/5RV/jv2OIKRjHJDbr5nd+mhTFp40gPVz5KlMz2N OPYf9yTJ0siBjWqgIhMySVURekGWkKYXRIYi66Ue6y45i8dp/G7m42lHdWrepGXq 6wdo4u5mL8SV64DZ7i1BcOnIkZ9cjWJ1J4hsmpBIu5gcpfLz8Pz3eNBB0Q+RSeYC nll3Kvc7VmipBeC0cXBiXOtethCJ9i+n17okYSKcgpr7HAR4bg55A0woHJ2enWC3 ggA==
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=FSoyRJfr4dk657+oUz8D/VvFwSND+Zs5brdufey1N xM=; b=DojN85YP32dGdsVv8kBvxOTUHrUfhx9gdyo+oIFucLvcxzw4TNfwtyrQn 2KFLmk0Ng9WPu32GQuCHELro+x3Zmiy+gkAApLIkVHqKgRUnwqpsKZOFW/xAR5Q9 7vTvyswq7fUfSpO6+HeMPZJj4n7MhHGsO1x5wbmDRtT3aY5yER2jWRMMLe05Sg3J i9p0Lci4W5u4CgkXiukp9dZJ4SbiXl3WH+mBTXQCDxcjIrsxnwpC2lvEro6xOFHh KNcIxXHLtuyXde6oDw3/bMgJdMYyIQJMnVrLEhC9Y286rD56wVTzaYi3ImUoklAD Fg7CgyX/7O2/1fj7VSLh7e0vJxRGA==
Message-Id:	<1542732771.1889363.1583400904.7F1A65BA@webmail.messagingengine.com>
From:	Ronald Fischer <ynnor AT mm DOT st>
To:	Ken Brown <kbrown AT cornell DOT edu>, cygwin AT cygwin DOT com
MIME-Version:	1.0
Subject:	Re: Bug: No json support anymore in Ruby 2.3.6
In-Reply-To:	<a6cd0bf6-e193-13ea-8584-264f20759ed9@cornell.edu>
References:	<1542703281 DOT 966819 DOT 1582906744 DOT 4CEC6D48 AT webmail DOT messagingengine DOT com> <f20f4cee-18cc-2e55-465a-31f547cfcbae AT cornell DOT edu> <e2df230a-cd42-36d1-c057-8ec8008be337 AT SystematicSw DOT ab DOT ca> <1542728354 DOT 1862120 DOT 1583295232 DOT 4B1A5F52 AT webmail DOT messagingengine DOT com> <a6cd0bf6-e193-13ea-8584-264f20759ed9 AT cornell DOT edu>
Date:	Tue, 20 Nov 2018 17:52:51 +0100
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id wAKGr67Q010779

Hi Ken.

I see your point .... For me, the foremost issue is to confirm, whether this is indeed a bug in the Cygwin package for Ruby, or not, and my posting on the mailing list was mainly intended to draw attention from the Ruby package maintainers (although other comments are, of course, also highly preciated, and in particular without your comment, I would not have known about the concept of default gems). 

I have to maintain a consistent state of our application accross several sites (Cygwin, Linux), and so far, only the new 2.3.6 Cygwin version, which I installed tentaively, has this problem. The previous version was correct in this respect, and all those versions I'm aware of, which run on Linux, also come with json built in. 

For the time being, we just avoid updating the Ruby version on Cygwin (because it seems to be nearly impossible to go back to the previous version once you have updated a package).

BTW, the definition of "default gems" provided on the stdgems site also includes the sentence that "one can not REMOVE them" (because they are bundled with Ruby), so I think it is even risky to deliver an explicit version of this gem as part of our application, which might then be in conflict with those installation which do contain the json gem in a different version. Furthermore, explicitly installing the json gem requires also to download the C compiler and the Cygwin library bindings for Ruby, because json contains C code. I rather would prefer not opening this can of worms....

Ronald

On Tue, Nov 20, 2018, at 17:26, Ken Brown wrote:
> On 11/20/2018 10:39 AM, Ronald Fischer wrote:
> > Hi Ken,
> > 
> > actually, the page regarding the gem list for the Ruby version in question (the one we have at Cygwin) is
> > 
> >      https://stdgems.org/2.3.6/
> > 
> > but this page too lists json as "default gem".
> > 
> > The page https://stdgems.org/ then defines this term as:
> > 
> > "Default gems: These gems are part of Ruby and you can always require them directly"
> > 
> > So from this I would conclude that json (and the other default gems) should be part of the Ruby installation, since "they are part of Ruby". If you disagree with my interpretation, please explain where I undersood the text in a wrong way.
> > 
> > BTW, I think that my viewpoint is also supported by
> > 
> > https://ruby-doc.org/stdlib-2.3.6/
> > 
> > which says that the packages listed on this page are found in the /lib directory of Ruby.
> > 
> > But even if I go along with your interpretation of the text, in that the default gems are delivered as a separated package, they should be available at least on the Cygwin server, and be installable from there, but I did a search for "ruby-default" and could not get a match.
> 
> I was just trying to tell you how to solve the problem.  I wasn't offering an 
> opinion about ruby packaging or which gems should be installed by default.
> 
> Ken
> ТÒÐÐ¥&ö&ÆVÒ&W÷'G3¢‡GG¢òö7–wv–âæ6öÒ÷&ö&ÆV×2æ‡FÖÀФd¢‡GG¢òö7–wv–âæ6öÒöfðÐ
> ¤Fö7VÖVçFF–ö㢇GG¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R–æfó¢‡GG¢òö7–wv–
> âæ6öÒöÖÂò7Vç7V'67&–&R×6–×ÆPРÐ

--
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

- Raw text -