On Wed, Jul 15, 2009 at 5:25 PM, Fran <francisb...@googlemail.com> wrote:
> > On Jul 15, 11:03 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > admin and example will be removed as you suggest. > > Thanks > > > welcome.w2p cannot be removed because it is the scaffolding app. > You can do this: Not version the *.w2p files, rather build them to: [1] make a release package; [2] let web2py check, and invoke "build" of them if needed on first startup from source. I know this implies "make" program issues, but that is something that can be dealt with slowly.... and should not be a roadblock in the long run (e.g. there are some more-or-less terrible build systems in python; Bruce is in the middle of designing one using decorators; eventually, there will be a "good enough" solution - even if we just need a *.w2p specific python command) Old, old (ancient) version control rule: NEVER VERSION DERIVED PRODUCTS Here's but one reason why... > > Can you at least not rebuild except when needed? > rev 1029 just added another copy when only sqlhtml.py was modified... > > > we'll make a new repo as soon as we move to mercurial. when do we move > > to mercurial? August? > > Can we keep a Bzr read-only version when the write version moves to > Hg? > - like we currently have an svn read-only vrsion of the original Bzr > master > I don't want to have to migrate my devs to Hg unless I really have > to... > > F > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
