From owner-freebsd-ports@FreeBSD.ORG Fri Feb 6 11:40:36 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6A8B16A4CE for ; Fri, 6 Feb 2004 11:40:36 -0800 (PST) Received: from prophecy.dyndns.org (pcp08490587pcs.levtwn01.pa.comcast.net [68.83.169.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 328E543D31 for ; Fri, 6 Feb 2004 11:40:19 -0800 (PST) (envelope-from apeiron@prophecy.dyndns.org) Received: from prophecy.dyndns.org (localhost.dyndns.org [127.0.0.1]) by prophecy.dyndns.org (8.12.10/8.12.10) with ESMTP id i16JeBDe005476; Fri, 6 Feb 2004 14:40:12 -0500 (EST) (envelope-from apeiron@prophecy.dyndns.org) Received: (from apeiron@localhost) by prophecy.dyndns.org (8.12.10/8.12.10/Submit) id i16JeB9E005475; Fri, 6 Feb 2004 14:40:11 -0500 (EST) (envelope-from apeiron) Date: Fri, 6 Feb 2004 14:40:11 -0500 From: Christopher Nehren To: FreeBSD Ports List Message-ID: <20040206194011.GA1000@prophecy.dyndns.org> References: <20040206173646.GA98792@prophecy.dyndns.org> <20040206183841.GB385@moo.holy.cow> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: <20040206183841.GB385@moo.holy.cow> User-Agent: Mutt/1.5.5.1i Subject: Re: Suggestion for distinction of XS Perl ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 19:40:36 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 06, 2004 at 13:38:41 EST, parv scribbled these curious markings: > A module is a module is a module. >=20 > If we will be having XS modules marked as stated above, i want to > have module ports marked which are already installed w/ a, 'a' as in > any, perl version. I'm not exactly sure of what you mean by this -- can you elaborate? > A port's files must have something that can identify it is a XS > port; something in pkg-descr, reference to compiler in Makefile, > pod, etc. I think that something like this[1]: find ${PORTSDIR} -mindepth 3 -maxdepth 3 -iregex '.*p5.*/pkg-plist' -exec grep -l '\.so$' {} \; would work as a good start. Granted, it won't get everything (razor-agents, for example), but it does get a lot of them -- approximately 240 or so on my machine. An alternative method is to have the XS Perl modules depend on a pseudo-port, and then you can "portupgrade -r perl-xs-package", and it'd do all of the work for you, like with pkg-config and GNOME (though that's not a pseudo-port at all, of course). [1]: If desired, I could write a Perl script to recurse through the ports tree and grep the Makefiles for PERL_CONFIGURE and the pkg-plist files for '\.so$'. This would probably prove to be a more definitive way to determine which ports use XS. If anyone knows of a better way to determine if a port is a Perl XS module, the information would be appreciated. --=20 I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Please CC me in all replies, even if I'm on the relevant list(s). --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAI+2bk/lo7zvzJioRAthmAKCk8NsDdjljz80hHksp1/AhywaNcgCgmnrY Qgbkm6bRJlzHe68vhLnxHUk= =O8qL -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK--