Submitting a Port Upgrade

[Aaron Dalton]

Doug Hardie wrote:
> I am totally confused.  The Porter's Handbook in section 3.6 says:
> 
> "Next, simply include the output of shar `find port_dir` in a bug  
> report and send it with the send-pr(1) program "
> 
> Ok.  I did that with an upgrade for qpopper.  I got back the  following 
> response:
> 
> "Please submit updates in "unified diff" format!
> You'll find instructions in the Porters Handbook. Then please submit  a 
> followup to this PR."
> 
> Huh?  What do you want?  I find no examples of unified diff format in  
> the Handbook.

Quote from Chapter 10:

If the maintainer asks you to do the upgrade or there is no maintainer, 
then you have a chance to help out FreeBSD by preparing the update 
yourself! Please make the changes and save the result of the recursive 
diff output of the new and old ports directories (e.g., if your modified 
port directory is called superedit and the original is in our tree as 
superedit.bak, then save the result of diff -ruN superedit.bak 
superedit). Either unified or context diff is fine, but port committers 
generally prefer unified diffs. Note the use of the -N option--this is 
the accepted way to force diff to properly deal with the case of new 
files being added or old files being deleted. Before sending us the 
diff, please examine the output to make sure all the changes make sense. 
To simplify common operations with patch files, you can use 
/usr/ports/Tools/scripts/patchtool.py. Before using it, please read 
/usr/ports/Tools/scripts/README.patchtool.

-- 
Aaron Dalton
aaron at FreeBSD.org
FreeBSD Ports Committer