New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
evolution-ews missing, needed for exchange support #12847
Comments
The closest thing I've found in any other distro's packaging is https://build.opensuse.org/package/view_file/home:dwmw2:evobits/evolution-ews/evolution-ews.spec, which I think lists out the files from |
I have interest in this. I also started packaging evolution-ews at one point: https://github.com/bjornfor/nixpkgs/tree/evolution-ews (haven't looked at it in a while). |
I just pushed 3db27f5, which I feel like is getting closer. In particular I now have some evolution-ews stuff showing up in
... however, still no "exchange" in the account setup dropdown ... :( |
@jerith666 you have to understand where does evolution look for modules. If it's only evolution nix store path, or also all the Also make sure to always check stdout, stderr and journalctl. |
I don't think it's
... and still no "exchange" entry in the account setup dropdown. I had (I also tried making a copy of the |
In case it helps, the dirs that actually got added to
|
@jerith666 I wasn't clear enough. I think evolution only uses the build-time directory to lookup for modules, which would be If that's the case, I think evolution should be patched to use a list of directories being provided at runtime (like |
Not ready to dive into patching evolution sources yet. The next thing I thought to try was using an FHS environment. So that's in the just-pushed ffcf86f, but it still doesn't work. :-/ |
comparing an
Inside the FHS env:
So it looks like in both cases all of their successful loads come from the |
How big is EWS? Maybe we can just build it with evolution-data-server? That is, build both at the same time and store in the same nix store path. I guess making EWS work in a separate store path requires patching it, something we can do later as an optimization. |
It's pretty small relative to the rest of evolution. I thought about this, but I think it would have to be built with both evolution-data-server and evolution, meaning (as I understand it) that those two large builds would have to be unified. At least, the expression I have for evolution-ews currently depends on both. |
@jerith666: You're right, EWS also depend on evolution. Aaargh! |
I applied some brute force and created a combined build of evolution-data-server, evolution and evolution-ews all in one nix store path. Now I have working Exchange email + global address list in Evolution. The calendar fails to load though. https://github.com/bjornfor/nixpkgs/tree/evolution-ews3 (I'm running GNOME3 desktop on NixOS. I'm unsure if it still works if this "super-build" of evolution is run on a system without Also, I asked upstream about the possibility of loading modules / plugins from external paths: https://mail.gnome.org/archives/evolution-list/2016-May/msg00235.html. Unsurprisingly, it's not possible yet. |
Pushed a fix to https://github.com/bjornfor/nixpkgs/tree/evolution-ews3 that unbreaks the calendar function (I made some typos earlier regarding install paths for ews plugin). |
Now the question is, how can this (mess) be upstreamed into NixOS? :-D |
as I need evolution with ews support: is there anything I can do to advance this pull request? |
@dfbm: "This" is just an issue, not a PR. If you're referring to https://github.com/bjornfor/nixpkgs/tree/evolution-ews3, then that needs a proper patch (that can be accepted upstream, or somehow be fairly maintainable if not accepted upstream) to allow building EWS into a separate path from the other evolution component(s). My hack of a "super build" in that tree isn't particularly nice. But it was the best I could do at the time. |
If you're enough of a gnome hacker to pursue the path of patching upstream to load its plugins from a runtime-specified path, that'd be ideal. But, IMO, after a year, it's a perfectly fine interim solution if @bjornfor's "super build" gets added to Some work is still needed, since as it stands now the existing |
Hi, |
I haven't done any more work on this myself. I think the minor cleanup I described in my previous comment is probably the minimum necessary before you could get an PR based on it to be accepted. (Though I'm not a committer so I can't say for sure.) |
@jerith666 I just tried to run
Would love to give it a try. If I can get it to work i'd love to try to somehow move this forward to land a PR |
@gilligan, that sounds like @bjornfor's work (https://github.com/bjornfor/nixpkgs/tree/evolution-ews3), not mine, that you're trying to run. Anyway, that's not an error I've seen before, I'm not sure what to make of it. |
Is there an expression that works with evolution 3.28? |
I haven't done any work on this recently, so nothing from me, no. :( |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
This issue has been superseded by #103135; closing. |
I've got a working nix expression for
evolution-ews
in https://github.com/jerith666/nixpkgs/tree/evolution-ews, however:evolution
andevolution-data-server
directories under/nix/store
I'm hoping for some guidance from the gnome maintainers, @jgeerds and @lethalman, about how to get this working. Thanks!
The text was updated successfully, but these errors were encountered: