[Pkg-drupal-devel] Package repository reorganization

dorileo ldorileo at gmail.com
Thu Dec 14 20:39:15 CET 2006


Hi guys

I`ve worked in a reorganization of the pkg-drupal, I hope that we`re going to 
win a lot in manageability working like I did(look, I hope).

My work was based in some drupal packages I`ve seen floating around but the 
fundamental point is: I would like to keep the upstream tarballed in a 
tarball directory, why? cause who maintains the software is the upstream we 
just write or accept some customizations and "hot"-bugfixes so we can track 
better the changes we`ve done and whenever we come to a new drupal(upstream) 
release we can see clearlly and easily what we`ve changed and how to better 
aproach the changes, but how? having a tarballed upstream in the repository 
and using debhelper to apply patches in the pacthes dir.

When synchronizing with a new upstream release we just download the tarball 
generate a new branch based in the actual trunk, change the trunk to use the 
new tarball and see the broken patches and start fixing them changing the 
customizations, verify the bugs to see if the fixes done in the package were 
already fixed/merged upstream(remembering that certainly the best thing is 
always follow the upstream development and send back the bugfixes to 
upstream :).

You can see my work here[1] and here[2]. Please note, I still have a little 
todo that I can "write down here" if you want. 

Please Coments.

1- http://www.dorileo.com.br/websvn
2- http://www.dorileo.com.br/package/drupal/

--
Dorileo



More information about the Pkg-drupal-devel mailing list