From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.129.92.65 with SMTP id q62mr9279949ywb.19.1457177875861; Sat, 05 Mar 2016 03:37:55 -0800 (PST) X-Received: by 10.182.246.104 with SMTP id xv8mr156415obc.1.1457177875773; Sat, 05 Mar 2016 03:37:55 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!w104no4993708qge.1!news-out.google.com!k1ni9344igd.0!nntp.google.com!hb3no11560341igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 5 Mar 2016 03:37:55 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=83.36.0.108; posting-account=Zsf4jwoAAADEqwCydv835KU9-S3h_Y26 NNTP-Posting-Host: 83.36.0.108 References: <60553d26-5829-46a4-8885-8b869a92e931@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <115210d7-9392-4b67-9d38-b8f462cf5003@googlegroups.com> Subject: Re: New Version of PragmARC.Text_IO From: jrmarino Injection-Date: Sat, 05 Mar 2016 11:37:55 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 3859 X-Received-Body-CRC: 2993471959 Xref: news.eternal-september.org comp.lang.ada:29678 Date: 2016-03-05T03:37:55-08:00 List-Id: On Friday, March 4, 2016 at 7:36:28 PM UTC+1, Jeffrey R. Carter wrote: > I'm glad this helped you. However, I haven't moved them to GitHub; rather= , I've > provided an alternative access path to the code through GitHub.=20 As long as it's keep it sync with the real repository, that's a synmantec i= ssue; the latest code is available via github. The movement had the immedi= ate benefit of making it suitable for bringing into ports (see below for th= e problem that existed before). =20 > There are 2 questions that apply here: which version of the PragmARCs you= 're > referring to, and what you mean by repository. The Ada-95 version comes w= ith a > set of test programs and some documentation, all provided through the mai= n site > for the components, pragmada.x10hosting.com. These are not part of the > components' code, and so not found at GitHub. But the primary documentati= on for > a pkg is in its spec. by "repository" i mean the entire contents of PramgARC in github. I could guess documentation in some for exists in specification or body of = the package, but when people say "documentation" they mean something that's= installed separately, something they can review without looking at the cod= e itself. I was basically stating an opinion that documentation as I just = defined it doesn't exist in repository (and you say not at all) and that Pr= agmARCs would be greatly improved with such documention. It's just an opin= ion. If it doesn't exist, there's nothing more I (as a packager) can do ab= out it. Hoewver, I had to struggle to even create the package description because t= hat didn't exist, but people have to know what the package does or they won= 't even try to install it. (see freshports URL for the description I made) > The beta version for ISO/IEC 8652:2007 comes as ZIP files with the year a= nd > month of the release as part of the file name. The branch at GitHub that > reflects this version contains the most recent of these. There's been no = change > to the Ada-95 version for several years so it exists as a single, undated= ZIP file. It should be trivial to tag github repository in the exact commits correspo= nding to tarballs so that obtaining code via tarball or via github results = in same content. It would not take long and I think it's useful, expeciall= y for OS packagers. I just looked at PragmARCs in any kind of detail yesterday. I packaged it = to help others discover and use it, and to help you get exposure for it. I= didn't directly benefit. The duplication to github definitely was benefic= ial for porting it though.