Hi,
so in my opinion the proposal is accepted. Now I will collect the
dependencies and I will come back to the lists, when it is integrated.
Currently known dependencies are :
- smoke test on Linux has to run with tar files
- automated test environment inside Sun has to be adapted
I think it will be started to work on such issues after the release of
OOo 3.0 Beta Refresh. So stay tuned ... :-)
Thorsten
Thorsten Ziehm wrote:
Hi,
in the past some requests came up to have also DEB packages beside RPM
packages, when a build from a Child Work Space (CWS) has to be tested
by the community.
This is a valid request, because the Linux Distributions with DEB
packages increased. But does it make sense to increase the time
for packaging the install sets on Linux, because two packages has
to be delivered?
The CWS tooling supports the functionality to pack a CWS as tar.gz
on Linux. Isn't this a valid format on Linux to exchange CWS builds
between community members?
The Proposal :
The default format for CWS builds on Linux should be tar.gz (instead of
RPM). It should still be possible to create install sets as RPM or DEB
or both.
The benefit :
- could be installed on Linux distros with RPM or DEB package management
systems (only untar the files)
- easy to remove
(only delete the directory/files)
The negative aspects :
- no system integration
- no testing of the Java Setup
- perhaps some automated installation tooling has to be adapted
In most cases the system integration and the Java setup are needed for
special testing areas only. So it shouldn't hinder testing general
CWS builds. And if it is needed the CWS owner can create RPM or DEB
packages on request.
If there aren't major objections, this will and can be changed soon.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
