@mizu: thanks. Now, please check if there was a ./debian directory created under the ./evolution-exchange-2.24.1, but I think this might be more of a rethorical question...
Here's the deal: when you 'apt-get source blah', 3 files are downloaded:
'apt-get source' will download the 3 of them, will untar the original and apply the diffs -- *iff* you have the development packages installed (at least devscripts, I think). This is important because (a) the Ubuntu install may want to put things at a slightly different place than the original upstream code; (b) we may have our own fixes to apply over the original.
Let's leave aside, for a moment, the issue of the ./debian directory. What you did -- './configure --prefix=/usr --enable-maintainer-mode && make && make install' (and you probably meant, for the last one, 'sudo make install') will bypass *all* Ubuntu customisations (if any). So... your install *may* be a bit different from a Ubuntu install. Your install may not have any additional patches applied.
And, of course, this may mean something. Or nothing.
Now, going back to the ./debian: *even* if you had it created, if you did a 'make && sudo make install' you would still not apply any Ubuntu fixes and changes tot he upstream source. Worse still, there is no guarateed way of backing out your local install (since it was done outside of dpkg/apt control.
You can find what is being changed locally by the Ubuntu package by looking at the ./debian and the ./debian/patches directories; a similar (but more difficult to follow) way is to look at the .diff file.
No matter what: if it is working as you built it, then it is something we can research, and try to find what is different.
@mizu: thanks. Now, please check if there was a ./debian directory created under the ./evolution- exchange- 2.24.1, but I think this might be more of a rethorical question...
Here's the deal: when you 'apt-get source blah', 3 files are downloaded:
- blah_version. orig.tar. gz ubuntuMod. diff.gz ubuntuMod. dsc
- blah_version-
- blah_version-
'apt-get source' will download the 3 of them, will untar the original and apply the diffs -- *iff* you have the development packages installed (at least devscripts, I think). This is important because (a) the Ubuntu install may want to put things at a slightly different place than the original upstream code; (b) we may have our own fixes to apply over the original.
Let's leave aside, for a moment, the issue of the ./debian directory. What you did -- './configure --prefix=/usr --enable- maintainer- mode && make && make install' (and you probably meant, for the last one, 'sudo make install') will bypass *all* Ubuntu customisations (if any). So... your install *may* be a bit different from a Ubuntu install. Your install may not have any additional patches applied.
And, of course, this may mean something. Or nothing.
Now, going back to the ./debian: *even* if you had it created, if you did a 'make && sudo make install' you would still not apply any Ubuntu fixes and changes tot he upstream source. Worse still, there is no guarateed way of backing out your local install (since it was done outside of dpkg/apt control.
You can find what is being changed locally by the Ubuntu package by looking at the ./debian and the ./debian/patches directories; a similar (but more difficult to follow) way is to look at the .diff file.
No matter what: if it is working as you built it, then it is something we can research, and try to find what is different.
A quick guide to packaging, and patching, for Ubuntu is at https:/ /wiki.ubuntu. com/PackagingGu ide.
Thank you.