After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 321881 - Version disaster in CVS
Version disaster in CVS
Status: RESOLVED NOTABUG
Product: evolution-data-server
Classification: Platform
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-11-19 20:29 UTC by Ali Akcaagac
Modified: 2006-01-30 06:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Ali Akcaagac 2005-11-19 20:29:05 UTC
Someone please explain why evolution-data-server when installed causes so much
version disaster ? After installation I usually end up in files and directories
ending with:

*-1.2
*-1.4
*-1.6

Can someone please decide and go with one version for the entire
evolution-data-server rather than having half a dozen different version numbers ?

From todays evolution-data-server CVS checkout and build (in a different prefix)
I ran a 'tree' on it and here a snipplet from what it installs and how it looks
like. Please note that this is what evolution-data-server installs, there is no
mixture with old previous installations or so.

.
|-- include
|   `-- evolution-data-server-1.6
|       |-- camel
|       |-- groupwise
|       |-- libebook
|       |-- libecal
|       |-- libedata-book
|       |-- libedata-cal
|       |-- libedataserver
|       |-- libedataserverui
|       `-- libical
|-- lib
|   |-- bonobo
|   |   `-- servers
|   |       `-- GNOME_Evolution_DataServer_1.2.server
|   |-- evolution-data-server-1.2
|   |   |-- camel-providers
|   |   `-- extensions
|   |-- libedataserver-1.2.la
|   |-- libedataserver-1.2.so -> libedataserver-1.2.so.4.1.1
|   |-- libedataserver-1.2.so.4 -> libedataserver-1.2.so.4.1.1
|   |-- libedataserver-1.2.so.4.1.1
|   |-- libegroupwise-1.2.la
|   |-- libegroupwise-1.2.so -> libegroupwise-1.2.so.8.0.3
|   |-- libegroupwise-1.2.so.8 -> libegroupwise-1.2.so.8.0.3
|   |-- libegroupwise-1.2.so.8.0.3
|   `-- pkgconfig
|       |-- camel-1.2.pc
|       |-- camel-provider-1.2.pc
|       |-- evolution-data-server-1.2.pc
|       |-- libebook-1.2.pc
|       |-- libecal-1.2.pc
|       |-- libedata-book-1.2.pc
|       |-- libedata-cal-1.2.pc
|       |-- libedataserver-1.2.pc
|       |-- libedataserverui-1.2.pc
|       `-- libegroupwise-1.2.pc
|-- libexec
|   |-- evolution-data-server-1.2
|   |   `-- evolution-data-server-1.4
|   |-- camel-index-control-1.2
|   |-- camel-lock-helper-1.2
|   `-- evolution-data-server-1.6
`-- share
    |-- evolution-data-server-1.6
    |   |-- glade
    |   |-- weather
    |   `-- zoneinfo
    |-- gtk-doc
    |   `-- html
    |-- idl
    |   `-- evolution-data-server-1.2
    |-- locale
    `-- pixmaps
        `-- evolution-data-server-1.6
Comment 1 Harish Krishnaswamy 2005-11-21 15:28:45 UTC
Well, your tree shows just two versions 1.2 and 1.6. the solitary 1.4 is most
probably a left-over executable from your previous installs. It is *not* from
the tarball. Maybe you can take a few deep breaths, smile a bit and try it again
:-).

1.2 is the API version for EDS libraries while 1.6 is the package version.
This allows clients to know what is the minimum-supported API and what extra
they get from a particular package (additonal bug fixes / subtler implementation
behaviors)

You have stated an opinion - [ dis·as·ter -  A grave misfortune ] but I could
use a more concrete problem statement as to how it exactly affects the user. May
be we can address it.

Comment 2 Ali Akcaagac 2005-11-24 02:10:24 UTC
Well it doesn't affect the user but it most likely affects the way you install
things or differently said. It affects the common version numbering paradigm of
GNOME.

Assume this problemcase, say you install an older Evolution and a newer
Evolution and both should coexists but both versions have an individual version
number (package number) but share the same API version number. The one
overwrites the other.

I know this explaination is a bit weak but I do hope you get the point on your
own here without making it a political something that requires me to fill in
pages of comments that might be closed as NOT A BUG anyways.
Comment 3 Ali Akcaagac 2006-01-27 03:17:57 UTC
Please close this report. The stuff has been explained fine enough.
Comment 4 Harish Krishnaswamy 2006-01-30 06:23:02 UTC
Ali, it is Evolution-data-server that has a package version and an API version, not Evolution. And yes, while it is possible for you to use an older Evolution and  install a newer one, it *is* largely untested and I would not recommend someone to have parallel EDS implementations on your machine, atm. The over-write _is_ intended till EDS has been tested stable on parallel version scenarios.