Yo, and Ian's Roadmap

[Ian Monroe]

On 9/13/06, Max Howell <max.howell at methylblue.com> wrote:
> > Anyways, if I have to be rebuilding half of KDE every day to keep up
> > with KDE4 development I may turn it into a dual-boot box anyways as
> > it's quite slow to rebuild all of kde on my laptop, but otherwise
> > it'll be a fast Windows box, so I can work on the Windows side of
> > things as well as other more normal Linux programming...
>
> May I suggest we build against the KDE 4 snapshot tarballs?
>
> Sure this may be a bit more work, but it'll be a lot less compiling,
> compiling that some of us cannot do everyday. And it also means we won't
> have situations where 2 developers have different compile bugs due to
> different revisions of kdelibs.
>
> Or possibly someone could make our own snapshots and then we could
> update once every few weeks?

Ok, I agree entirely. Tarballs aren't really necessary, anyone
following our SVN could pick out a SVN revision to use from kdelibs.
We could declare what SVN revision number that amarok currently
compiles againist and just change that once every few weeks.

We would have to make the kdelibs revision very obvious with a
filename or something for marauding KDE hackers.

The alternative is to develop againist Krash and whatever future
snapshots are made. Does anyone following this stuff know if that
makes sense or not?

Ian Monroe