On 2007/09/23 18:30, Paride Legovini wrote: > The second question reveals my newbie status as a maintainer. I am quite > sure a couple of nights ago I read on the porting documentation (maybe > on the checklist) that one needs to follow -current in order to maintain > a port. Now I can't find that sentence again, can you confirm it? Anyway
Yes, new/updated ports should be done against -current (tar.gz if it's a new port - preferably send a cvs diff if it's an update - if unsure about whether your mail client breaks the formatting, send it to yourself first and check it applies cleanly - tar.gz if it's new). > I feel like following -current, I'm just not sure if I prefer the > snapshots or building everything from cvs (as I'm doing by now -- very > time consuming). Snapshots aren't being built at the moment, so updating to the most recent snap and building from updated CVS is the way for now. When they resume that's quite an easy way to follow development of the base OS, but for ports work, you still usually want to fetch the ports tree by cvs (either anoncvs, or cvs against a local repository mirrored by cvsync or cvsup). With cvs diff, you can easily prepare a diff with added/removed files by using cvs add/rm and cvs diff -uNp (it gets messy if you add/rm directories, but works well for e.g. changing patch files in an existing directory).
