[typo] Recent Multi-Blog update Breaks
cedric at feelfree.homelinux.com
Fri Mar 17 13:20:36 EST 2006
On my point of view, single blog is just a particular case of a multi-blog
implementation. This should becomes the default typo blog with a default
setting to "single blog" for all people who want to install their personal
typo. But I don't know if it's possible... if not there must be 2 different
It's just my humble opinion, to bring some ideas to community.
Le Vendredi 17 Mars 2006 18:00, Gary Shewan a écrit :
> On 17 Mar 2006, at 16:19, Piers Cawley wrote:
> > "Kevin Kubasik" <kevin at kubasik.net> writes:
> >> Just a note, I found that when attempting to update to the
> >> latestTrunk, rev 915 breaks (it can't seem to add the new blogs
> >> tablecorrectly) 914 is good though. It seems to me that a multiblog
> >> branchshould be handled that way, in its own branch, not in the
> >> trunk(although the comment seems to imply that it is being done in
> >> abranch, maybe im just SVN illiterate)
> > It's staying in the trunk -- the comment about the branch was from my
> > local SVK based repository which I'd not edited out.
> > What errors were you getting when you tried to run the migrations?
> > Could you send me a the relevant log section?
> > --
> > Piers Cawley <pdcawley at bofh.org.uk>
> > http://www.bofh.org.uk/
> > _______________________________________________
> > Typo-list mailing list
> > Typo-list at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/typo-list
> Sigh, well that's me not upgrading in trunk. Multi blog support is
> bloat for those of us running Typo on single sites. I think it's a
> bad move to keep this in trunk. If you want me to throw a penny in
> I'd say split it now. The initial attraction of Typo because it was
> lean. Why keep multi blog in trunk when not everyone wants it? It's
> screaming out for a separate branch.
> God I hate bloat.
> Typo-list mailing list
> Typo-list at rubyforge.org
More information about the Typo-list