a common release effort

[Thomas Friedrichsmeier]

Hi,

thanks! It's great know that a release is coming up, and it's great to see 
that there is a plan for sharing the work on multiple shoulders.

Unfortunately, at the moment, I'm too busy with other priorities to step 
forward and help. However I do hope to participate in a later release (or in 
case this one takes longer than expected). A few questions:

On Thursday 09 December 2010, Patrick Spendrin wrote:
> Currently I have added the following compilers:
> mingw4, mingw-w32, msvc2008 and msvc2010.

As far as I understand, mingw-w32 is MinGW 4.x 32bit. So what exactly is 
mingw4? Is this 64bit?

> - Those interested in it, would set up a build environment with their
> preferred compiler dedicated to the release (I can give the settings of
> the build server as hints as well).

I guess that might be helpful. The first question I have is exactly which 
versions of packages should be built (ok, you can look at the dashboard to see 
which versions get built, there, but having it explicitely, would be nice).

Is there a simple way to tell emerge to work on the 4.5.4 target, globally, or 
do you need to specifiy
  --target=4.5.4
for each package, individually?
 
> - The Server would run and fail on a certain package, you can see that
> on the release dashboard
> (http://www.winkde.org/pub/kde/ports/win32/dashboard/release/).

The links to the logs only work for mingw-w32, for me. 404 on all others.

> - Somebody would step up and fix this error locally:
> * You can create a patch with
> 
> > emerge --createpatch --target=4.5.4 kde-4.5/kdetoys
> 
> * The patch can be found under
> %KDEROOT%\build\kde-4.5\PACKAGENAME-PACKAGEVERSION.
> * You would add this patch to the emerge package under
> emerge\portage\kde-4.5\kdetoys and also change the .py file by adding a
> line like:
> self.patchToApply['4.5.4'] = [('kdetoys-4.5.4-20101209.diff', 1)]
> into the subinfo section.

What does the ', 1' stand for? What's the syntax for adding multiple patches?

> - After the patch has been applied, the buildserver would svn up his
> emerge directories, retry the build with the now fixed package, succeed
> and package & upload this package.

Last I heard, kdelibs, and kdebase will probably move to git before christmas. 
Are there plans for moving kdesupport / emerge?

> If you have any comments about that, just send them.

Again, thanks for all your work! I hope I'll have some time to help, next 
time.

Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-windows/attachments/20101210/88ea80a4/attachment.sig