Aug. 13, 2011
7:06 a.m.
On 12 August 2011 23:32, Damien Pollet <damien.pollet@gmail.com> wrote:
On 12 August 2011 22:21, Lukas Renggli <renggli@gmail.com> wrote:
The only solution is to stick with consistent and well though package name scheme. Not the only possible naming strategy, but the one we developed for Seaside works pretty well: http://code.google.com/p/seaside/wiki/PackageNaming
I know about these conventions, but how do I proceed towards them? :)
Closing the eyes and restarting from scratch. We did that too with the Seaside packages at some point. Lukas -- Lukas Renggli www.lukas-renggli.ch