The CVS tutorial is pretty good in my opinion, yet it doesn't handle questions a new developer like me keeps asking himself. It should mention how to do correct header tags for ebuilds and changelogs, it should mention to change Changelog files too when committing ebuilds and it should let people know to cvs add digest files too. A mention on how to handle cvs manipulation in general should also be included. Like how to correctly update package.mask, not to screw with important ebuilds without consulting/asking for testing and such. I have seen some entries on mailing lists where senior developers kinda "bitch" about newbies breaking rules, but noone cares about letting newbies know about the rulez and obviously newbies can't know what has been established as "rule of thumb" by pratice, so the situation won't improve.
Stocke, You were asking questions about CVS the other day, what better a way to learn? hehe, just kidding. Please work on this and *keep me informed*. Thanks! //ZhEN
aahhh I get it ok, this is not a problem with the cvs gide the cvs guide is great, for people who wanna learn to use cvs...what we need is to get everything together to make our "New Gentoo Linux Developers" guide a guide to get new devs up to speed on everything they need to know
Yeah, we need to do that. //ZhEN *** This bug has been marked as a duplicate of 8032 ***