dp2mp-move branch work done & merging into trunk

Juan Manuel Palacios jmpp at macports.org
Fri Jun 1 11:48:21 PDT 2007

(same mail as before, resent with a proper subject!)

	Good afternoon everyone! At long last, I consider the work on my  
dp2mp-move branch almost 100% done, 99.99% lets say ;-)

	Here's a doc explaining all the implications moving to these sources  


	I'd love to get as much feedback as possible on all the renaming and  
moves, and an overall opinion of how things look like in a standard  
MacPorts installation after upgrading to this branch. I ask because  
this branch moves stuff like "/opt/local/var/db/dports/sources/ 
rsync.rsync.darwinports.org_dpupdate_dports" to "/opt/local/var/ 
macports/sources/rsync.macports.org/release/ports", as explained in  
the wiki doc, so if the chosen new paths are not what the majority  
regards as the best choice, corrections could be easily made before  
these sources are distributed to the masses.

	It is my intention to merge all of the branch back into trunk ASAP,  
after consensus is reached on best "new conventions", since people  
writing code against current trunk will surely have to rewrite some  
parts of it after this is merged, albeit changes will hopefully be  
small. Nevertheless, I'd very much like to minimize this negative  
(and quite hateful, I understand) side effect.

	And finally, I say "almost 100%" and not "100%" because there are  
still a couple of small pending things, detailed in the "Pending"  
section of the doc. Taking care of them shouldn't take too long at  
all (remaining 0.01% ;-)



PS: The branch mirrors trunk minus sfiera's latest commit, which we  
could easily merge. Therefore merging should be painless, other than  
the drawback detailed above. Also, branch has been tested extensively  
and everything works "as expected", but please do not hesitate to  
send me any feedback/error reports. Thanks!

More information about the macports-dev mailing list