Re: [opensuse-buildservice] Status: openSUSE Build Service
On Tuesday 11 September 2007 15:30:02 wrote John Pye:
Hi Adrian,
Couple of questions...
Adrian Schröter wrote:
* build.o.o currently does not use encryption. We can switch to https, there are no speed problems expected. We can not offer http and https at the same time. Decision to switch. AI: adrian coordinate with Matt
Does HTTPS support pipelining? That could be a source of slowdown for users, if not.
AFAIK it should not make a difference here, ssl is just one layer on top of http to get https.
* Discussion about the urgency of build support for MacOS X and MS Windows in the build service. AI: adrian get feedback from PM.
I'd be interested to hear a little more about what is being considered for this. I'd also like to suggest that some improvements to the support for Debian package repositories be improved: it is currently AFAICT not possible to integrate Debian packages build with an APT repository, and this would be a really useful feature.
Uuh ... you mention something I broke during server upgrade and did not fix yet due to lots of other stuff :/ if anyone has building sources for SLE 10 of apt-ftparchive binary/package, I can fix this within seconds ....
Regarding Windows support: how would you propose to specify package dependencies, given that no such support for this exists natively?
I have no real ideas about that. There do exist some approaches out there for that, but this is definitive the first thing what needs to get defined. Yes, it will need quite some work to support this, I am sure. But imaging the new number of users, which we will attract :) bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, 11 Sep 2007, Adrian Schröter wrote:
Regarding Windows support: how would you propose to specify package dependencies, given that no such support for this exists natively?
I have no real ideas about that. There do exist some approaches out there for that, but this is definitive the first thing what needs to get defined.
Yes, it will need quite some work to support this, I am sure. But imaging the new number of users, which we will attract :)
What about starting with cygwin-support? Ciao -- http://www.dstoecker.eu/ (PGP key available)
Dirk Stoecker wrote:
On Tue, 11 Sep 2007, Adrian Schröter wrote:
Regarding Windows support: how would you propose to specify package dependencies, given that no such support for this exists natively?
I have no real ideas about that. There do exist some approaches out there for that, but this is definitive the first thing what needs to get defined.
Yes, it will need quite some work to support this, I am sure. But imaging the new number of users, which we will attract :)
What about starting with cygwin-support?
Obviously much to be considered on this matter; I was thinking a bit about it, so I thought I would send my thoughts. 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 :-) And obviously you'd need someone to pay for all those Windows licenses (or else you could try ReactOS and/or Wine?) 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'. 'windows.build' would be some kind of file containing build-time information: how to unpack the sources, how to initiate the build, and a list of prerequisite packages and versions. As with RPM .spec file and Debian 'control' file, this stuff would be external to the sources. 'windows.package' would be some information about how the resulting package could be identified (eg where it can be found at the end of the build process), how it can be installed (in silent/unattended mode, specifically), how it can be uninstalled, and how it can be identified/checked (post-install checks). It would also contain a list of runtime prerequisites. To actually implement all that, you could write a miniature package manager. It could be given a .build or .package file as an argument, and could download and install the necessary dependencies then build the required package, and optionally report the results back to the Build Service (for the case that it was being run on a build host). This little package manager would also be useful for people wanting to use Windows software hosted on the Build Service: they would be able to download .package files (signed, presumably) and the installer would deal with the installation of the package including dependencies, with a configurable package repository URL or URLs. The package manager would have to optionally provide a windows 'service' that could be used for two-way communication with Build Service, eg to tell it when a virtual host had completed its boot-up and was ready to receive build commands. After the package manager had been written, the next thing would be to create some of the initial packages such as MinGW tools etc. They could be created as binary packages, just uploading the installer and the .package file somewhere. Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
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
Hi Klaas, Klaas Freitag wrote:
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 ?
Done. Feel free to edit/expand.
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?
WPKG seems to be heavily focussed on centralised adminisatration of machines, rather than providing dependency management to the end-user. It might be a starting point, perhaps. Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thursday 13 September 2007 05:02:27 wrote John Pye:
Hi Klaas,
Klaas Freitag wrote:
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 ?
Done. Feel free to edit/expand.
Can you please create extra pages for the branch/merge concept and the windows build concept ? These are complete different topics IMHO and I would like to avoid to discuss all OBS concepts in one wiki page, it would become quite long ;) good morning adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Adrian, Adrian Schröter wrote:
On Thursday 13 September 2007 05:02:27 wrote John Pye:
Hi Klaas,
Klaas Freitag wrote:
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 ?
Done. Feel free to edit/expand.
Can you please create extra pages for the branch/merge concept and the windows build concept ?
These are complete different topics IMHO and I would like to avoid to discuss all OBS concepts in one wiki page, it would become quite long ;)
Done. See here: http://en.opensuse.org/Build_Service/Concepts Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thursday 13 September 2007 10:17, John Pye wrote:
Done. See here: Very cool, thanks :)
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
participants (4)
-
Adrian Schröter -
Dirk Stoecker -
John Pye -
Klaas Freitag