question about /usr/ports structure

[Tim Aslat]

Hi All,

I'm wondering if someone can enlighten me on the /usr/ports directory
structure for development.  What I'm looking for is a place I can put
ports I'm working on until they are ready for submission, without
having them overwritten each time I cvsup my ports tree (daily cron job)

Setting aside something like /usr/ports/local would be nice, or is there
a better option?

cheers

Tim

-- 
| The most exciting phrase to   | Tim Aslat <tim at spyderweb.com.au> |
| hear in science, the one that | http://www.spyderweb.com.au      |
| heralds new discoveries, is   | Spyderweb Consulting             |
| not "Eureka!" (I found it!)   | P: 82243020    M: 0401088479     |
| but "That's funny ..."        | Webmaster for                    |
|          -- Isaac Asimov      | http://www.goodiesruleok.com     |
| No, "Eureka" is Greek for     | The Ultimate Goody Fansite       |
| "This bath is too hot!        | admin at goodiesruleok.com          |
|           -- Dr Who           |                                  |