From owner-freebsd-ruby@FreeBSD.ORG Mon Jun 6 16:36:15 2011 Return-Path: Delivered-To: ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F31B1065670 for ; Mon, 6 Jun 2011 16:36:15 +0000 (UTC) (envelope-from romain@blogreen.org) Received: from 23.mail-out.ovh.net (23.mail-out.ovh.net [91.121.28.222]) by mx1.freebsd.org (Postfix) with SMTP id E80028FC12 for ; Mon, 6 Jun 2011 16:36:14 +0000 (UTC) Received: (qmail 29975 invoked by uid 503); 6 Jun 2011 16:06:52 -0000 Received: from marvin.blogreen.org (178.33.173.42) by 23.mail-out.ovh.net with SMTP; 6 Jun 2011 16:06:52 -0000 Received: by marvin.blogreen.org (Postfix, from userid 1001) id 4D728202E9; Mon, 6 Jun 2011 18:09:31 +0200 (CEST) Date: Mon, 6 Jun 2011 18:09:31 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: ruby@freebsd.org Message-ID: <20110606160931.GA17343@blogreen.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline X-PGP-Key: http://romain.blogreen.org/pubkey.asc User-Agent: Mutt/1.5.21 (2010-09-15) X-Ovh-Tracer-Id: 18094337404831910484 Cc: Subject: Fixing gem files permissions X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2011 16:36:15 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello I would like to know if there is some 'standard' way for the rubygems-* ports for fixing wrong files permissions. It appears that getopt-declare (not in the ports tree, it's a dependency of another port I would like to push) install files in a weird fashion: ------------------------------8<--------------------------- =3D=3D=3D> SECURITY REPORT:=20 This port has installed the following world-writable files/directorie= s. /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /getopt-declare.gemspec /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /samples/cmdline_singles.rb /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /samples/cmdline_array.rb /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /samples/cmdline_usage.rb /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /test/test_cmdline_parameters.rb /tmp/rubygem-getopt-declare-1.29/lib/ruby/gems/1.8/gems/getopt-declare-1.29= /README.txt [...] ------------------------------8<--------------------------- My current workaround is: ------------------------------8<--------------------------- post-install: @${FIND} ${PREFIX}/${GEM_LIB_DIR} -type f -exec ${CHMOD} 444 '{}' ';' ------------------------------8<--------------------------- I am not really happy with this. Is there a better way to fix this? I am not used with Ruby gems packaging, and I would like to be sure that this is a problem that should be signaled upstream before acting: is it? Thanks! Romain --DocE+STaALJfprDB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQGcBAEBAgAGBQJN7Pu4AAoJELpNHZVREjNv1/UMAKmq4OwtnVWfctzAM/+Tf9Vy MJB1XuB+/LNDtGP5p9VFiTxS9PSoOhgVhJsrpA4XSyyFVSNbvP4H44ekcENwIAze irAuIXQXt6zlI0znloxLIC/tlva4DpZ1PSO2iq1Yho35yz61SqWzRUlgqKAwijyt mtAeUzhWH2QAN+5gVqVeqzrVLHxuAbL7hYR+4uI8s3qGNBg8w9rul2yPU+mff3dj Y3CqhWU94zQRREr6xX3ZlWGdhVNWudTWwFQB8Qrpr8qdiK5av/6NFewYVe94sYoD O+V1dhLOHG6hGmg//d5n5Pjj6wMXo2Uvid6hczKqTxQB1PyhAhFAuGC25MiannOB UpU9UVCwSiS+rIMs054yAasNxfVRL9U0wRx7u2zfG9mOf+Y1qlwp6XXOWL/gaUnm /yqG6tPNGgxnDtqMo+YZ4kcOqR9v9z5Gt1s2tkd4D3N8m4FsG4vqa4+e3zeEbK62 NoFZkqFzAtge2RiLbmi+aIacKLPiCk7oenPonPzZsw== =N6sR -----END PGP SIGNATURE----- --DocE+STaALJfprDB--