From owner-cvs-all Wed Aug 26 18:41:41 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07373 for cvs-all-outgoing; Wed, 26 Aug 1998 18:41:41 -0700 (PDT) (envelope-from owner-cvs-all) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07355; Wed, 26 Aug 1998 18:41:30 -0700 (PDT) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca6-88.ix.netcom.com [205.186.213.88]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id SAA23743; Wed, 26 Aug 1998 18:40:40 -0700 (PDT) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id SAA10753; Wed, 26 Aug 1998 18:40:28 -0700 (PDT) Date: Wed, 26 Aug 1998 18:40:28 -0700 (PDT) Message-Id: <199808270140.SAA10753@silvia.hip.berkeley.edu> To: committers@freebsd.org CC: ports@freebsd.org, markm@freebsd.org Subject: p5-* ports From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-cvs-all@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hiya, Many p5-* ports are still broken due to the perl5 upgrade. While it's easy to avoid building those (DUDS="$(echo p5-*)"), they are causing other ports that use them as dependencies to break as well. In particular, those who committed the "fix" to hardcode "5.00501" in your ports, those are (predictably) broken again now. We have a framework to deal with those now (${PERL_VER} and ${PERL_VERSION} in Makefile, %%PERL_VER%% and %%PERL_VERSION%% in PLIST and manpage auto-append to PLIST), please take a look at the latest bsd.port.mk or any of the devel/p5-* ports (which I fixed). Ports fixed that way should survive future perl5 upgrades. I know it has been an unwanted burden to you all to suddenly have this come crashing down on you, but the tree really cannot stay broken very long. Please fix them at your earliest convenience. Thanks. Satoshi P.S. BTW, will it be easier for people to tell which ones are broken if I just mark those BROKEN?