Date: Wed, 08 Feb 2012 10:02:44 -0800 From: perryh@pluto.rain.com To: portmgr-feedback@freebsd.org, dougb@freebsd.org Cc: ports@freebsd.org Subject: Re: FreeBSD ports which are currently scheduled for deletion Message-ID: <4f32b8c4./c%2Bg1eePU5396RYF%perryh@pluto.rain.com> In-Reply-To: <4F31ECFC.4030007@FreeBSD.org> References: <201202070829.q178TNZw081740@portsmonj.FreeBSD.org> <4f324a97.Hab0ctxtpiOZet2I%perryh@pluto.rain.com> <4F31ECFC.4030007@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton <dougb@freebsd.org> wrote: > On 02/08/2012 02:12, perryh@pluto.rain.com wrote: > > linimon@freebsd.org wrote: > >> portname: graphics/vrml2pov > >> description: Convert VRML files to POVRay source > >> maintainer: ports@FreeBSD.org > >> status: BROKEN > >> deprecated because: unfetchable > > This seems to be a ports-infrastructure problem, rather than a > > problem in the vrml2pov port. > No, it's a "No one cares enough about this port to step forward > and maintain it" problem. Er, as of a few hours ago (when I tried it), the URL in the distfile link on vrml2pov's download page *exactly* matched the URL that the port tries to fetch. This does not appear to be a case of the distfile having been moved and the port not having caught up: the port is using exactly the same URL to (try to) fetch the distfile as any human would, but it works for the human because browsers understand redirections. The only reason the port doesn't fetch is that the infrastructure doesn't handle that kind of URL properly. Given that, why would it not make more sense to fix the broken ports infrastructure -- thereby also covering any number of other and/or future similar cases -- rather than "fixing" this one port that is not actually wrong? > > The infrastructure needs to handle redirections. > > That's arguable, but once again it's an issue that no one has > stepped up to fix. Likely because it would involve grubbing around in bsd.port.mk, which only portmgr@ is allowed to touch :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f32b8c4./c%2Bg1eePU5396RYF%perryh>