On 11/30/2009 01:06 AM, Oswald Buddenhagen wrote: > you increase the barrier for "involuntary early adopters". today i do > "svn up extragear" and get the newest thing with all the rest. when more > projects start to break out before we have a working submodule > architecture to "keep everything together", it will start being a real > pita at some point. effectively, you lose visibility as part of kde.
In my experience, the vast majority of people who use Konver- sation from the SCM have a checkout of the individual sub-di- rectory. In fact, we regularly get comments along the lines of "wow, cool that I don't have to co -n the module super- structure first" on IRC. Likewise, distributions that offer live packages that fetch Konversation's sources from the SCM, like Gentoo, do this on a per-app basis, and are prepared to handle git repositories already. Nonetheless, your point that we'd inconvenience people who currently get their Konversation by way of a single check- out of the entirety of Extragear is a salient one and some- thing to think about. I guess it's a whole other debate how module-y Extragear really is in practice. Do people really think in terms of "I'll get myself the extragear-network set installed now", or is it just a way to logically orga- nize the folder structure in SVN, an issue that goes away with git? -- Best regards, Eike Hein _______________________________________________ Kde-scm-interest mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-scm-interest
