[Kolab-devel] Packaging
Bernhard Reiter
bernhard at intevation.de
Thu May 13 11:09:13 CEST 2004
On Wednesday 12 May 2004 21:37, Stuart Bingë wrote:
> On Wednesday, 12 May 2004 21:27, Stuart Bingë wrote:
> > On Wednesday, 12 May 2004 21:22, Bernhard Reiter wrote:
> > > It should be possible to create RPMs for testing
> > > and if we want to be really quick after a fix
> > > so for some situations we should keep the possibility.
> >
> > Although isn't what you describe the job of OpenPKG?
> >
> > As far as I understand it, we should just create a new release tarball
> > when we need to update, and let OpenPKG create the SRPM (which we can
> > then grab from OpenPKG-current).
>
> Apologies for the double post.
>
> My above comment was for official releases - I guess it would be beneficial
> to have this functionality for testing though. We can easily add the
> functionality in.
There you go. ;-)
> However, I definitely think we should ensure that no RPMs we create through
> this mechanism be used *in any way* as official releases. This is exactly
> the confusion that we've been experiencing in the past, which has ended up
> in version hell.
In my perspective we had many reasons for the version confusion.
1.
No webpage which really explained stuff.
2.
No changelog
3.
No common version number
4.
No clear versioning /naming scheme.
5.
Unclear directory structure.
and so on.
You are right, we need to make the status of each package clear.
Usually this is done by the name and the placement in the right directory.
Still we want people to have access to the development versions,
snapshots, betas, release candiates and so on for testing purposes.
> In other words, the RPMs created through this devtool mechanism should
> never end up on official distribution sites - we should flag them as such
> so that anyone who uses one knows that it is a development RPM, and that it
> has *absolutely nothing* to do with an official release.
Yes.
We also need to clean up what version are out there.
I also lack the overview here.
AFAIK Kolab 1.0.x (which is at 1.0.8 + security fix) is used at some places.
This was the most heavly tested release so far and I still consider it stable.
Next there is Kolab CF which Codefusion has some maintained servers.
Next are the Openpkg releases which I overall consider "beta"
and the Mandrake packaged version which I cannot say much about.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2145 bytes
Desc: signature
URL: <http://lists.kolab.org/pipermail/devel/attachments/20040513/13860638/attachment.p7s>
More information about the devel
mailing list