Date: Sun, 28 Nov 2010 16:09:21 GMT From: Aldis Berjoza <aldis@bsdroot.lv> To: freebsd-gnats-submit@FreeBSD.org Subject: docs/152645: Improve Porters Handbook. Explaing sourceforge links Message-ID: <201011281609.oASG9LmO043503@red.freebsd.org> Resent-Message-ID: <201011281610.oASGACMB033888@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 152645 >Category: docs >Synopsis: Improve Porters Handbook. Explaing sourceforge links >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Nov 28 16:10:12 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Aldis Berjoza >Release: >Organization: >Environment: >Description: One must update Porters Handbook to explain how to convert sourceforge download link for use in ports Makefiles... So far, when I was porting something from sourceforge writing correct download URL was the biggest, problem.... There is absolutely no information about this. Yesterday, for the first time, I saw information, that actually helped me to port app. It was javascript by amdmi3@ http://userscripts.org/scripts/review/50136 After I looked at this script, it was finally clear to me, how to convert Stupid Sourceforge URL's A colourful example would probably be the best (since not everyone know regexp) I Set severity "serious" and priority "High", because I think this info will help many new porters... and maybe even old porters. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011281609.oASG9LmO043503>