[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Build instructions on KDE TechBase for 4.x release or BRANCH
From: Michael Pyne <mpyne () purinchu ! net>
Date: 2008-08-29 19:58:55
Message-ID: 200808291559.00024.mpyne () purinchu ! net
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
[Attachment #4 (multipart/alternative)]
On Friday 29 August 2008, Matthew Woehlke wrote:
> Allen Winter wrote:
> > On Friday 29 August 2008 14:56:02 Matthew Woehlke wrote:
> >> Tom Albers wrote:
> >>> The release team is considering making two tags which contain the
> >>> stuff (kdesupport parts) you need for KDE stable and trunk. Can we wait
> >>> for that to happen before discussing this even more? The idea is that
> >>> you can check out that tag and have all the right versions.
> >>
> >> ...and will simply building the latest trunk/kdesupport still work, I
> >> hope?
> >
> > The whole point will be to stop using trunk/kdesupport. That's where
> > the development takes place. We should be building only against
> > stable external packages.
>
> Meh, but then I have to worry about *upgrading* them ;-). Right now I
> just build the latest rev. of the whole enchilada. (And it's a LOT more
> convenient to have one kdesupport than phonon+plasma+strigi+automoc+...)
Well although they call it a tag it is quite possible to bump code in these
tags. When a new phonon is required for trunk, for example, they could simply
unlink the trunk-stable/phonon and copy the new stable phonon over it. It
doesn't have to be static for all time.
> Besides, for those willing to do it, I'd think it's better to have more
> people banging on head before release cycles kick in, no?
I think this is so we can get closer to "summer in trunk" myself. By focusing
more testing attention on kdesupport we necessarily subtract from the trunk we
*should* be focusing on, /trunk/KDE. ;)
Besides which, those who are willing to do it can still build trunk/kdesupport
like always. The new tag would be for those who are tired of having random
kdesupport modules break their whole build. :)
Regards,
- Michael Pyne
[Attachment #7 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" \
"http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" \
content="1" /><style type="text/css"> p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Consolas'; font-size:11pt; font-weight:400; \
font-style:normal;"> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">On Friday \
29 August 2008, Matthew Woehlke wrote:</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> Allen Winter wrote:</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > On Friday 29 August \
2008 14:56:02 Matthew Woehlke wrote:</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> >> Tom Albers wrote:</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> >>> The release \
team is considering making two tags which contain the</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> >>> stuff (kdesupport parts) you \
need for KDE stable and trunk. Can we wait</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> >>> for that to happen before \
discussing this even more? The idea is that</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> >>> you can check out that tag and \
have all the right versions.</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> >></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> >> ...and will simply building the latest \
trunk/kdesupport still work, I</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> >> hope?</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> ></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> > The whole point will be to stop using \
trunk/kdesupport. That's where</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> > the development takes place. We should be building only \
against</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > \
stable external packages.</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">> Meh, but then I have to worry about *upgrading* them ;-). \
Right now I</p> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> just \
build the latest rev. of the whole enchilada. (And it's a LOT more</p> <p style=" \
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> convenient to have one \
kdesupport than phonon+plasma+strigi+automoc+...)</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Well although they call it a \
tag it is quite possible to bump code in these tags. When a new phonon is required \
for trunk, for example, they could simply unlink the trunk-stable/phonon and copy the \
new stable phonon over it. It doesn't have to be static for all time.</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Besides, for those \
willing to do it, I'd think it's better to have more</p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">> people banging on head before release cycles \
kick in, no?</p> <p style="-qt-paragraph-type:empty; margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;"></p> <p style=" margin-top:0px; \
margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; \
text-indent:0px; -qt-user-state:0;">I think this is so we can get closer to "summer \
in trunk" myself. By focusing more testing attention on kdesupport we necessarily \
subtract from the trunk we *should* be focusing on, /trunk/KDE. ;)</p> <p \
style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; \
margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"></p> <p \
style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; \
-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Besides which, those who are \
willing to do it can still build trunk/kdesupport like always. The new tag would be \
for those who are tired of having random kdesupport modules break their whole build. \
:)</p> <p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"></p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;">Regards,</p> <p style=" margin-top:0px; margin-bottom:0px; \
margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; \
-qt-user-state:0;"> - Michael Pyne</p></body></html>
["signature.asc" (application/pgp-signature)]
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic