From owner-freebsd-ports@FreeBSD.ORG Tue Aug 11 15:36:58 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 901D1106566B for ; Tue, 11 Aug 2009 15:36:58 +0000 (UTC) (envelope-from erwin@mail.droso.net) Received: from mail.droso.net (koala.ipv6.droso.net [IPv6:2001:6c8:6:c:20d:56ff:fe6f:f935]) by mx1.freebsd.org (Postfix) with ESMTP id 2682C8FC48 for ; Tue, 11 Aug 2009 15:36:57 +0000 (UTC) Received: by mail.droso.net (Postfix, from userid 1001) id 0353E1CC5F; Tue, 11 Aug 2009 17:36:56 +0200 (CEST) Date: Tue, 11 Aug 2009 17:36:56 +0200 From: Erwin Lansing To: freebsd-ports@freebsd.org Message-ID: <20090811153655.GJ25687@droso.net> References: <20090811152054.GB50944@hades.panopticon> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="l3cnbd11D/TCH+Qu" Content-Disposition: inline In-Reply-To: <20090811152054.GB50944@hades.panopticon> X-Operating-System: FreeBSD/i386 7.2-STABLE User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: SourceForge changing file distribution scheme! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2009 15:36:58 -0000 --l3cnbd11D/TCH+Qu Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 11, 2009 at 07:20:54PM +0400, Dmitry Marakasov wrote: > Hi! hi Dmitry, >=20 > I've noticed that SF is changing file distribution scheme significantly, > and I guess that will affect many ports and maybe infrastructure. I fear the same, unfortunately. However, I haven't as yet been able to identify a consistency in the new scheme. Is it only new files that are put in the /project/ folder? Will all files slowly migrate to the new file structure? Or is there something different internally in SF whether something is a project or just a file? >=20 > As you can see, the distfile now redirects to another path and also > another mirror. As fetch doesn't follow redirects by default, this won't > work. My idea is that in addition to [old scheme] >=20 > MASTER_SITE_SOURCEFORGE+=3D \ > http://${mirror}.dl.sourceforge.net/sourceforge/%SUBDIR%/ >=20 > we'll need to add >=20 > MASTER_SITE_SOURCEFORGE_NEW+=3D \ > http://${mirror}.dl.sourceforge.net/project/%SUBDIR%/ >=20 > with coresponding macro (SF -> SFNEW) >=20 > and we'll have to add pretty complex MASTER_SITE_SUBDIR to each updated > port from SF. >=20 I have received a similar patch from Sylvio Cesar, but this only fixes the issue with the directory changing from sourceforge to project, it doesn't address the changing of servers you also showed in the example. This bit is more tricky, and I haven't found a way to predict the final server/link yet unfortunately. I hope someone out there is better at guessing this than me and can come up with a patch for both issues. Cheers, -erwin --=20 Erwin Lansing http://droso.org Prediction is very difficult especially about the future erwin@FreeBSD.org --l3cnbd11D/TCH+Qu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFKgZAXqy9aWxUlaZARAngqAJ9pZF+l389n88Mdc+kyadxi3AdMJACgqEpn KtCr1e/n1JEWFmirEJhfSs4= =1WKk -----END PGP SIGNATURE----- --l3cnbd11D/TCH+Qu--