<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Feb 17, 2007, at 6:25 PM, Benoit Gagnon wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">What I'm favoring, globally, is to completely separate the bundles</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">from the application. Updating TM would not include new bundles.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Downloading it the first time either, but instead would pop the bundle</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">manager to ask for bundles to download.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">It's true that svn log will give me detailed changes to the bundles.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">But it won't tell me easily what's new from the previous version I had</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">(I'd need to note down the revision I'm at first). Version control</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">logs are also rarely effective from an end-user perspective. I don't</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">see many applications dumping me their SCM log as "release notes"</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">whenever I update it.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">As for the support directory, I don't see why it couldn't be a bundle itself.</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Sorry for opposing some of you guys in this discussion; I'm really</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">excited about this new bundle system and I want to make sure my ideas</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">are dropped in the pre-prod pool :)</DIV></BLOCKQUOTE></DIV><DIV><BR class="khtml-block-placeholder"></DIV>As far as I can tell, we're not disagreeing.<DIV><BR class="khtml-block-placeholder"></DIV><DIV>What we currently have is two systems for managing bundles.</DIV><DIV><SPAN class="Apple-style-span"><B>#1 </B>Either you use the bundles that ship inside TextMate or </SPAN></DIV><DIV><SPAN class="Apple-style-span"><B>#2 </B>you manually manage the bundles yourself.</SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>With option#2 you do have the bundles completely separate from the application.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>What I think we're proposing is a way to merge the two options into one.</DIV><DIV>So that people with absolutely no clue can still get more bundles and keep them updated, without having to wait for a new build of TextMate.</DIV><DIV>And people that know what all is going on aren't frustrated and end up resorting to doing it manually themselves.</DIV><DIV><DIV><BR><DIV>thomas Aylott — <B>subtleGradient </B>— CrazyEgg — sixteenColors</DIV></DIV></DIV></BODY></HTML>