[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-devel
Subject:    Re: The releases after 2.0 and string changes..
From:       "Dan Meltzer" <parallelgrapefruit () gmail ! com>
Date:       2008-12-05 14:12:35
Message-ID: 46059ce10812050612j662272baw4f64cbcf9834ceec () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, Dec 5, 2008 at 8:29 AM, Casey Link <unnamedrambler@gmail.com> wrote:

> On Fri, Dec 5, 2008 at 8:25 AM, Jeff Mitchell <kde-dev@emailgoeshere.com>
> wrote:
> > Dan Meltzer wrote:
> >> 2) You will either need to maintain two separate build directories or
> >> have to deal with a full rebuild every time you switch branch checkouts.
> >
> > That has not been my experience.
> >
>
> Ditto. It just rebuilds everything that is different between the two
> branches, which may require a full build but in most cases it doesn't.


Alright, even better.

It still might make sense to maintain separate build directories between 2.0
and 2.1 as I have a feeling they will diverge fairly quickly, leaving lots
of changes between the branches that require lots of rebuilding.

My branch setup original was with 1.4 and 2.0... No wonder it forced a full
rebuild :)

>
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel@kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>

[Attachment #5 (text/html)]

<br><br><div class="gmail_quote">On Fri, Dec 5, 2008 at 8:29 AM, Casey Link <span \
dir="ltr">&lt;<a href="mailto:unnamedrambler@gmail.com">unnamedrambler@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Fri, Dec \
5, 2008 at 8:25 AM, Jeff Mitchell &lt;<a \
href="mailto:kde-dev@emailgoeshere.com">kde-dev@emailgoeshere.com</a>&gt; wrote:<br> \
&gt; Dan Meltzer wrote:<br> &gt;&gt; 2) You will either need to maintain two separate \
build directories or<br> &gt;&gt; have to deal with a full rebuild every time you \
switch branch checkouts.<br> &gt;<br>
&gt; That has not been my experience.<br>
&gt;<br>
<br>
</div>Ditto. It just rebuilds everything that is different between the two<br>
branches, which may require a full build but in most cases it \
doesn&#39;t.</blockquote><div><br>Alright, even better. <br><br>It still might make \
sense to maintain separate build directories between 2.0 and 2.1 as I have a feeling \
they will diverge fairly quickly, leaving lots of changes between the branches that \
require lots of rebuilding.<br> <br>My branch setup original was with 1.4 and 2.0... \
No wonder it forced a full rebuild :) <br></div><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;"> <br>
<div><div></div><div \
class="Wj3C7c">_______________________________________________<br> Amarok-devel \
mailing list<br> <a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/amarok-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a><br> \
</div></div></blockquote></div><br>



_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel


[prev in list] [next in list] [prev in thread] [next in thread]