From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32094 invoked by alias); 9 Feb 2016 17:10:14 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 30436 invoked by uid 89); 9 Feb 2016 17:10:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-96.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_PBL,RDNS_DYNAMIC,USER_IN_WHITELIST autolearn=no version=3.3.2 spammy=ACK, H*F:U*corinna-cygwin, Hx-languages-length:3451, H*R:U*cygwin-apps X-HELO: calimero.vinschen.de Received: from ipbcc0d020.dynamic.kabel-deutschland.de (HELO calimero.vinschen.de) (188.192.208.32) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 09 Feb 2016 17:10:13 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id AB03DA8051D; Tue, 9 Feb 2016 18:10:10 +0100 (CET) Date: Tue, 09 Feb 2016 17:10:00 -0000 From: Corinna Vinschen To: cygwin-apps@cygwin.com Subject: Re: setup.hint documentation issues Message-ID: <20160209171010.GC25261@calimero.vinschen.de> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <56B9E71A.7010002@dronecode.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <56B9E71A.7010002@dronecode.org.uk> User-Agent: Mutt/1.5.24 (2015-08-30) X-SW-Source: 2016-02/txt/msg00017.txt.bz2 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 3528 On Feb 9 13:18, Jon Turney wrote: >=20 > While I've been looking at replacement/improvement for the current upset > script, I've come across some minor issues related to under-specification= or > under-documentation of setup.hint: >=20 > * The encoding of setup.hint is unspecified. >=20 > Historically both ISO-8859-1 and UTF-8 have been used. (e.g. libspiro used > 'b=C3=A9zier' with an ISO-8859-1 e-acute, whereas calligra-l10n-nb uses '= Bokm=C3=A5l' > with an UTF-8 a-ring. Various other hints use UTF-8 punctuation marks) >=20 > I think currently UTF-8 displays correctly in the HTML package pages, but > neither encoding displays correctly in setup. >=20 > I'd suggest that we specify UTF-8 and eventually fix setup to handle that. ACK > * 'sdesc' text is mangled in setup.ini (but not the HTML package list) >=20 > In particular, it is forced to start with a capital letter (which is > incorrect when the sdesc starts with a command name which is properly > lower-case, e.g. "dash shell", etc.), and any text up to and including the > first colon is removed, presumably in an effort to prevent people writing > the package name again, (which mangles perl and ruby module names in the > description, e.g. "Ruby Net::HTTP persistent connection support", ""Perl > Math::Int64 distribution", etc.) >=20 > I'd suggest this mangling is removed, and sdesc starting "packagename:" is > explicitly reported. Sounds good, but where is this mangling performed? Upset? > * Handling of double-quoted text seems over-complicated >=20 > A multi-line double-quoted value is terminated only by a double-quote at = the > end of the line, and embedded double-quotes are silently transformed to > single-quotes (e.g proj had a sdesc of ""The PROJ Cartographic Projections > Software (utilities)", where the erroneous nested double-quote was being > transformed to a single-quote) >=20 > There is no escaping of embedded double-quotes, and no way to represent o= ne. >=20 > Additionally, spaces after the leading quote are magically removed. >=20 > Additionally, genini requires that sdesc and ldesc are double-quoted, but > upset does not. >=20 > I'd suggest that double-quoting of those keys is made mandatory, and > embedded double-quotes are forbidden, as this permits simpler processing = of > this text, lexing character by character. What about existing packages? > * It's not very clear what 'skip' represents >=20 > The description "The skip line indicates that that package should not app= ear > in setup. It is intended for directories that exist in the hierarchy that > should not be considered." is a bit vague to me. >=20 > It's not totally clear if it's intended for indicating directories which > should be empty, source-only packages, or something else. >=20 > upset knows enough to omit packages which have no install tarfiles (i.e. = are > source-only) from from setup.ini, irrespective of 'skip'. >=20 > However, the presence of 'skip' also causes the package to be omitted from > the HTML package list. >=20 > I think cygport's behaviour has changed over time, but currently will mark > source-packages as 'skip', however there are several packages that are > source-only (e.g. attica), that are missing 'skip'. IMHO we don't need "skip". A source-only package should be automatically skipped anyway. What other reason do we need to ignore a package? Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature; name="signature.asc" Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWuh1yAAoJEPU2Bp2uRE+gNqsP/Ruy3UPLSecj4GznRL9pAUir JDKCxKSRhnaRZpoRz6KIAM+KeN/oxhWWilUZ/K3p7wzBswOLNhN8dmvHHkeFcaC8 vbIaD2xJ+7jYJZTDi3bRFAqDxGXvWqQMWbifa/QVEI4MTd7NgWTHBVK5/MMwabkG lLGVPrRKerx2M2er3KWuUbQgzlPjqlPH0zhPFF/XLKgHSSyLsIiPQn2/7aijhP+/ QBTU0Kkj6yyr6wVR+Gu78QqI2893+Q7jwjW1f+YIEwIeTQOfSpJtFf8XqwJ3+q2p s04TwRXhPa8ynKIUGCwXS1R2+YpMX1z/cbdlDvlQsLF4qQAE/OjcYR2o5CaZ+m43 FkHpGJhKepGHmh0+kzJHF+/3ohLJ4ajxfd3Kbht9NVlRMBSZwvbu0BK1YzynbChh /y74J5PMRSQKZBYJybmjBYk8E3rF18S3IuVM/B+VwlI9q+UJjQCMWiD3T8sNyFVC bilawbLZ81vNBAko1BWlm/3XcVqagqUqV5cjq5ktv3TMVf0huNEbkJwAYilZPwDW WKwty9aZG1u9mhIBXOMHI7qEFBrC1uo+T7eGBEW9TPQ3OZ3cPB5fjLiVeKrsjKQk tQWWUSEoeyFjlT6x8AfD9IMW19rIFWFJKgmkKU5Jl1D0/Tg3C31nEUkBoTAEA1SR AN3raOznnUhOIf9AGMOs =FG6e -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o--