Bug 20648

Summary: link in /usr/ports/README.html is outdated
Product: Ports & Packages Reporter: Vivek Khera <khera>
Component: Individual Port(s)Assignee: Satoshi Asami <asami>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
vivek.vcf none

Description Vivek Khera 2000-08-16 17:30:03 UTC 
	

The link to porting guidelines in the third paragraph of
file:/usr/ports/README.html points to the handbook, which say to look
elsewhere for the doc (it has moved).

The new link should be to http://www.freebsd.org/porters-handbook/index.html

Also, shouldn't these links point to local copies rather than the
remote web site directly (with such a link as an option for latest versions)?

Fix: 

update the link as described.
How-To-Repeat: 
	
n/a
Comment 1 Chris D.Faulhaber freebsd_committer freebsd_triage 2000-08-18 14:03:05 UTC 
State Changed
From-To: open->closed

README.html's are not part of the ports repository, they are 
generated files.  If you wish to update them, type 'make readme'.
Comment 2 Chris D.Faulhaber freebsd_committer freebsd_triage 2000-08-18 14:03:05 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-ports

Misfiled PR
Comment 3 Vick Khera 2000-08-18 16:04:34 UTC 
Ok, then type "make readme" and you'll still see the busted link.  So I
got the file name wrong, but the link is still stale.  Didn't you even
bother to look at it or just knee-jerk response that "README.html is not
part of ports"?
Comment 4 Chris D.Faulhaber freebsd_committer freebsd_triage 2000-08-18 16:17:01 UTC 
State Changed
From-To: closed->open

Ooops, the links are out of date (though not necessarily invalid). 

This is the PW's territory
Comment 5 Chris D.Faulhaber freebsd_committer freebsd_triage 2000-08-18 16:17:01 UTC 
Responsible Changed
From-To: freebsd-ports->asami

Over to PW
Comment 6 Satoshi Asami freebsd_committer freebsd_triage 2000-08-18 18:18:36 UTC 
State Changed
From-To: open->closed

Thanks, fixed. 

By the way, the reason why it's not referring to the local copy 
is that this file changes very quickly and we have had a lot of problems 
with people submitting ports according to old guidelines.  (People who 
know how to keep their local docs up to date also know where to find them. :)