Good news

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

Good news
by suy on Tuesday 31/May/2005, @08:07

That's great.

Its a pity that installing Kolab is so difficutl/strange. I've been desiring to try it since I started to actively use kaddressbook and korganizer, but my email accounts don't support sieve, so I'm still using local files and POP accounts.

I hope in the future we can see tarballs of Kolab, and more easy to install/package, instead of that strange openpkg and RPMs.

Related Links

·   Articles on KDE Official News
·   Also by suy
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Good news
by stumbles on Tuesday 31/May/2005, @09:28

I agree on the point about source tarballs, minus the rpm stuff. Unless I am mistaken (it does happen :) ), doesn't the source tarballs have to be created to make the RPMS?

As it is, it tends to either leave the source distros out in the cold or jump through a bunch of hoops just to extract the source from the rpms.

[ Reply To This | View ]

Re: Good news
by andrianarivony on Tuesday 31/May/2005, @10:20

I don't understand. I've found the Kolab setup very clean and easy: one script to launch, a few questions to answer. What strange with that?

[ Reply To This | View ]

Re: Good news
by Andy on Tuesday 31/May/2005, @23:16

i guess it's somewhat strange to have two packaging systems side-by-side, one deb and rpm. and for most (like me) rpm isn't part of their daily work, so they have to learn that, too. it's easy, no big difference, just an other db structure, but it's a psychological barrier.
but Kolab install doesn't require any knowledge about rpm, since the scripts take care of everything.

[ Reply To This | View ]

Re: Good news
by Anonymous on Wednesday 01/Jun/2005, @01:08

There exist more than two systems package systems: "gg:site:distrowatch.com package management -rpm -deb -src"

[ Reply To This | View ]

Re: Good news
by suy on Wednesday 01/Jun/2005, @07:29

See KDE for example. You can compile the sources, and install them wherever you like. I have KDE installed both from the standard packages of my distribution, and from source, under ~/kde/local (so they don't collide one with the other).

KDE is very easy to package (at least, applications). If you take a look at

http://www.fruitsalad.org/kolab/server/beta/kolab-server-2.0-rc-2/ix86-debian3.0/

You'll see RPMs... for Debian!

I want just a tarball with some source, and some user defined prefix for installation. The README says that the installation is going to /kolab, instead of following the FHS. Also, have in mind that you need patched versions of some applications. This is pretty ugly for packaging purposes. Why I need to download again apache?

[ Reply To This | View ]

Re: Good news
by Martin Konold on Wednesday 01/Jun/2005, @17:02

just for completeness:

The prefix is arbitrary in Kolab 2. So you may for example set it to /usr/local/kolab or /opt/kolab if you happen to prefer these paths.

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Ironically, we are working on that right now!" -- Kurt Granroth
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.