From owner-freebsd-ports@freebsd.org Wed May 30 18:05:10 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 222E0FCAD76 for ; Wed, 30 May 2018 18:05:10 +0000 (UTC) (envelope-from jkeenan@pobox.com) Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BDBF77089F for ; Wed, 30 May 2018 18:05:09 +0000 (UTC) (envelope-from jkeenan@pobox.com) Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id A6108EF890; Wed, 30 May 2018 14:00:43 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=Ef7J3NUcH9Os zZG6ZkHHt7hfmdA=; b=pXYSgE28FRMrqNVYBsMXaxZEzvMG6f2zhQRVb/bpuUE+ 1vavdS4PYrNqyeUyzsM8Cc33NlLIHSTRRBnTw/0YIpfIu67hrY7XQbmr4uvDzIlf 8upTkIO9S75D2/EKeQyxLOfeN1dZfpDWHfxh3C4Jz1fCRFTFHG0TrJLzXS/TRog= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=Abryee yvioo7mhX+bUYwnLvhmwxQhQo2k/IjIZ0BTDjrxb0sJFOsKMZo3cpugggpzhK2VN 2KVOvGpIr5t2oSYj3g4Ob0s4kQW6T75AfIkyx+LfiY24i6rW5CaUSHTft05h6ApN ISwaSdx5u2BDDgkm7xsbob3oxE+94YrVGfD/A= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 9E68BEF88F; Wed, 30 May 2018 14:00:43 -0400 (EDT) Received: from [192.168.1.5] (unknown [24.185.115.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 24C36EF88E; Wed, 30 May 2018 14:00:42 -0400 (EDT) Subject: Re: search.cpan.org is going away (replaced by MetaCPAN) To: Greg Kennedy , freebsd-ports@freebsd.org References: From: James E Keenan Message-ID: <2c553d68-1e6a-a01a-03c4-d8c9119ba97b@pobox.com> Date: Wed, 30 May 2018 14:00:36 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 5E3F9410-6433-11E8-81CE-44CE1968708C-57062903!pb-smtp1.pobox.com X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2018 18:05:10 -0000 On 05/30/2018 01:53 PM, Greg Kennedy wrote: > Found this news item today relating to Perl: > https://log.perl.org/2018/05/goodbye-search-dot-cpan-dot-org.html > > In short, search.cpan.org is being retired on June 25, with the > replacement MetaCPAN website to take its place. At that time they > will transparently redirect all URL requests to comparable MetaCPAN > pages. > > FreeBSD porting style usually requires that the URL for Perl modules > (in pkg-descr) be set to something like... > > ##### > WWW: http://search.cpan.org/dist/CPAN-Testers-Common-Client/ > ##### > > While these links will (theoretically) continue working, we should > think about a mass find-replace in all "*/p5-*/pkg-descr" URL fields > to point to new MetaCPAN URLs. Also, the Porter's Handbook / portlint > / etc would need to be updated to recommend using MetaCPAN URLs > instead of the existing search.cpan.org links. > > I didn't see any other discussions on this in the past couple months > of the mailinglist archive so I thought I'd raise the issue here :) > > -Greg > Gret, thank you for calling attention to this. My hunch is that once search.cpan.org has been retired, we should take a sample of the URL fields in the pkg-descr field and verify the links they actually resolve to (as distinct from what they are currently *expected* to resolve to). At that point, a mass find-replace becomes feasible and testable. Thank you very much. Jim Keenan