port maintaince procedural questions

[Matthew Donovan]

On Sun, Jun 01, 2008 at 08:49:15PM -0400, Aryeh M. Friedman wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I have brought a older port maintained by ports at freebsd.org to the 
> current version.... I have done all the work needed to make it 
> committable.... I have several questions first:
> 
> 1. How do I take maintainership of the port?
> 
> 2. How do I submit the patch to bring it upto date? (I know for new 
> ports I do PR with a special subject but in a case like this).
> 
> Just so people know the port in question is devel/tailor I upgraded it 
> from 0.9.32 to 0.9.34 because 34 has added 3 or so more back ends.
> 
> As to the reason for asking for taking the maintainership is the ports 
> 2.0 team needs it for internal development (we use aegis internally and 
> need to translate to cvs).
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.9 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iEYEARECAAYFAkhDQ4sACgkQk8GFzCrQm4D7JACg2HYyxjzMrhOmCRKfjIYCTR4x
> C0YAn10z8fYSu7kjbADjNO6YvlXx2VMG
> =iz6w
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
This is what I do anymore when I update a port I test it with porttools and I copy the new port directory to something like <port>.new and leave the old port as is then I run port submit. 

It will make the patch if it can find the older port and you fill out the PR and it will then ask to send it abort or nothing. it's the easiest way I have found.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20080602/b5a103c7/attachment.pgp