Bradley Giesbrecht wrote: > > Working in a svn tree is definitely the easiest way for you to collaborate > with your fellow MacPorts contributers. > > If you were to run your script in a svn checkout of trunk/dports you would be > able to provide the desired diff with "cd dports && svn diff > > patch-perl5.16.diff". > > If you add the file:///trunk/dports tree to sources.conf you can hack and > build to suit your own needs and "port sync" or "cd dports && svn up" will > pull in changes leaving you to decide how to handle conflicts.
OK ... I'll give it a try :-) I haven't got that much experience with svn, git, hg beyound the basics. Actually, what the two of us did with your hg is the most advanced I've ever worked with version control !!! :-O Now, when I've got that file, how / where do you want it ??? > > Regards, > Bradley Giesbrecht (pixilla) :-) -- Bjarne D Mathiesen København N ; Danmark ; Europa ---------------------------------------------------------------------- denne besked er skrevet i et totalt M$-frit miljø MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3 _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
