May 2007 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Should we evaluate Zimbra ? - a next-gen Mail Server
by Alexey Eremenko 11 May '07

11 May '07

It seems that Zimbra arrived: The Next-Gen mail server, similar to GMail in concept and powerful features, but Open-Source, and installable in the Enterprise (not just on the Internet). That is: Zimbra, like GMail is both a mail server, mail client and HTTP server, which makes it possible to connect to Zimbra from any Web browser, but it can be connected from any emailing client (like Thunderbird). Zimbra has also integrated support for Calendars. It can give serious combat to Microsoft Exchange, and other (older) Linux email servers. Now if we this type of server, we should evaluate it more closely. I haven't evaluated it, just seen their flash demos. (and liked them a LOT! ) I'm as a Home user don't need an email server at Home. I use GMail. But this can make a revolution within an Enterprise. -- -Alexey Eremenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] openssl package split
by Matthias Koenig 07 May '07

07 May '07

Hi, to follow the library packaging policy the openssl package has been branched with the following new package layout: openssl -----+--> openssl | +--> libopenssl0_9_8 | +--> openssl-certs openssl-devel --> libopenssl-devel openssl-doc --> openssl-doc Since libopenssl-devel provides openssl-devel, there is currently no need for an immediate change for packages which BuildRequires openssl-devel. But please consider changing your BuildRequires tag from openssl-devel to libopenssl-devel when touching your package next time in the future. Note, that the devel package does not depend anymore on the openssl package itself, which contains the /usr/bin/openssl binary. Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] [library packaging policy] Example fixing of curl
by Richard Guenther 02 May '07

02 May '07

For the library packaging policy as discussed previously this is an example on how to fix an offending package. We take the example of curl, as we have (ick) compat-curl2 and compat-curl3 packages alread, which is a mess. Curl currently is split into curl providing the /usr/bin/curl binrary and the /usr/lib64/libcurl.so.X library and a curl-devel package with development files. The library packaging policy forces you to split off a libcurl4 package with just the libcurl.so.4* shared libraries. The library packaging policy forces you to rename curl-devel to either libcurl-devel or libcurl4-devel if you want to support development with different curl versions. We choose not to and rename it to libcurl-devel which will depend on libcurl4 for this version. For the renaming you need a proper Provides: curl-devel and Obsoletes: curl-devel dependency for update to work. The split off of libcurl4 does not require anything special as shared lib requirements will take care of what is necessary. [Yes, I've started on the above, no need to do it for curl, but please consider fixing your package early if you ever had the need to provide compat-* packages and fix your package the next time you touch it otherwise] Thanks, Richard. -- Richard Guenther <rguenther(a)suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

7 14