On Wednesday 12 September 2007 11:15, John Pye wrote:
Dirk Stoecker wrote: Hi,
Obviously much to be considered on this matter; I was thinking a bit about it, so I thought I would send my thoughts. Thanks, that's great. This is a huge area of problems, but somehow we have to start and I think this is a good starting point.
What about adding this to http://en.opensuse.org/Build_Service/Concepts ?
If Windows support were to be offered, presumably the goal with that would be to facilitate porting/testing of Linux-based software onto Windows, rather than providing a big fat build farm for generic projects from the windows community :-) Yes to the first goal, but I would not lock out the second goal as well.
And obviously you'd need someone to pay for all those Windows licenses (or else you could try ReactOS and/or Wine?) Sure, that must be sorted out of course.
There would need to be some meta-info related to each package for Windows. In the same way that you have debian.rules, debian.changelog and debian.control, you might have 'windows.build' and 'windows.package'. I agree.
To actually implement all that, you could write a miniature package manager. [...] That is - as far as I got knowledge about the bs backend so far - what
the bs_worker does. That needs to be ported to Windows somehow, right. The problem is that we have a dependency aware system on linux etc., but not on Windows which complicates the problem a lot. But there must be already solutions to that out there (how, for example are projects like Eclipse or the Apache tools doing that?) - a short search lead me to http://wpkg.org/index.php/Main_Page . I haven't looked into that in detail yet. Any experiences? have fun, Klaas -- Klaas Freitag Architect OPS/IPD SUSE LINUX Products GmbH - Nuernberg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org