Re: [Evolution-hackers] e-d-s 2.32.0 error during make install
On Fri, Nov 12, 2010 at 1:18 AM, Sasa Ostrouska wrote: > Ok, I have applied the patch I found here: > https://bugzilla.gnome.org/show_bug.cgi?id=628238 > > but no luck, now I get that error: > > make[5]: Leaving directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal' > make[4]: Leaving directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal' > make[3]: Leaving directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal' > Making install in libedata-cal > make[3]: Entering directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' > make install-am > make[4]: Entering directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' > make[5]: Entering directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' > test -z "/usr/lib64" || /usr/bin/mkdir -p > "/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64" > /bin/sh ../../libtool --mode=install /usr/bin/ginstall -c -s > libedata-cal-1.2.la > '/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64' > libtool: install: warning: relinking `libedata-cal-1.2.la' > libtool: install: (cd > /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal; > /bin/sh > /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/libtool > --silent --tag CC --mode=relink gcc -O2 -fPIC -pipe -march=x86-64 > -version-info 10:0:0 -Wl,--no-undefined -o libedata-cal-1.2.la -rpath > /usr/lib64 libedata_cal_1_2_la-e-data-cal-enumtypes.lo > libedata_cal_1_2_la-e-cal-backend.lo > libedata_cal_1_2_la-e-cal-backend-cache.lo > libedata_cal_1_2_la-e-cal-backend-factory.lo > libedata_cal_1_2_la-e-cal-backend-intervaltree.lo > libedata_cal_1_2_la-e-cal-backend-sexp.lo > libedata_cal_1_2_la-e-cal-backend-sync.lo > libedata_cal_1_2_la-e-cal-backend-util.lo > libedata_cal_1_2_la-e-cal-backend-store.lo > libedata_cal_1_2_la-e-cal-backend-file-store.lo > libedata_cal_1_2_la-e-data-cal.lo > libedata_cal_1_2_la-e-data-cal-view.lo > ../../calendar/libegdbus/libegdbus-cal.la > ../../calendar/libecal/libecal-1.2.la > ../../libedataserver/libedataserver-1.2.la > ../../libebackend/libebackend-1.2.la -pthread -lgio-2.0 -lgobject-2.0 > -lgmodule-2.0 -lgthread-2.0 -lrt -lical -licalss -licalvcal -lxml2 > -lgconf-2 -lglib-2.0 -inst-prefix-dir > /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1) > .libs/libedata_cal_1_2_la-e-cal-backend-file-store.o: In function > `e_cal_util_get_component_occur_times': > e-cal-backend-file-store.c:(.text+0x170b): undefined reference to > `e_cal_recur_ensure_end_dates' > e-cal-backend-file-store.c:(.text+0x1946): undefined reference to > `e_cal_recur_obtain_enddate' > e-cal-backend-file-store.c:(.text+0x19cf): undefined reference to > `e_cal_recur_obtain_enddate' > collect2: ld returned 1 exit status > libtool: install: error: relink `libedata-cal-1.2.la' with the above > command before installing it > make[5]: *** [install-libLTLIBRARIES] Error 1 > make[5]: Leaving directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' > make[4]: *** [install-am] Error 2 > make[4]: Leaving directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' > make[3]: *** [install] Error 2 > make[3]: Leaving directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' > make[2]: *** [install-recursive] Error 1 > make[2]: Leaving directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar' > make[1]: *** [install-recursive] Error 1 > make[1]: Leaving directory > `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0' > make: *** [install-strip] Error 2 > Error! Configure exited with status: 2 > Failed package evolution-data-server > > r...@quadser:/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG_2_32# > > Any ideas ? > Rgds > Saxa > Ok sorry , I'm stupid, I forogot to autoreconf after I installed the patch. Solved it. Rgds Saxa ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubsc
Re: [Evolution-hackers] Rethinking account management
On Wed, 2010-11-10 at 16:20 -0500, Matthew Barnes wrote: > On Thu, 2010-11-11 at 09:16 +1300, Andrew McMillan wrote: > > Does this mean (for example) that we will be able to have a caldav > > server, with credentials, and then just associate (and maybe > > auto-discover) all of the user's addressbooks, calendars, todo-lists and > > journals which the user has on that server? > > I honestly don't know if that's possible with a CalDAV server (I'm just > not familiar enough with CalDAV), but if we're talking about a groupware > service... Yes, it is. Apple iCal (for example) will discover and show all of a user's calendar collections. The contacts app on an iPhone (with iOS 4.1) will discover and show all of a user's addressbooks if that DAV server also does CardDAV. Calendar collections may very well also store VTODO and VJOURNAL data (DAViCal does, for example, as well as supporting CardDAV in very recent versions). So Evolution, with SMTP, IMAP, CalDAV and CardDAV servers really is a complete groupware service. Newer extensions to CalDAV/CardDAV also add support for service discovery through SRV lookups for _caldav, _caldavs, _carddav, _carddavs services and URL locating through requests against /.well-known/carddav or /.well-known/caldav URLs after the server discovery. > Currently each of our groupware backends has to invent this kind of > account management for itself. All I'm proposing is a general framework > that backends can utilize to make it easier and more consistent. > > Auto-discovery is also up to each backend to implement, and rightfully > so. But the framework certainly allows for discovered data sources to > be associated with the account. > > I hope I answered your question. Like I said, handling of groupware > accounts is still kinda hand wavy at this point. I think so. Evolution was early to the party when CalDAV came out as a specification, but the support in there has not evolved very well to follow the current possibilities. That said, the biggest complaint I hear about Evolution's CalDAV support is it's lack of a useful 'offline' mode. I'm currently in the process of developing caldav/carddav setup and synchronisation process (for another purpose) but once that's working it might be worth looking at that with a view to seeing if we can improve the structure of CalDAV setup within Evolution. I know Milan has done some good work on CalDAV (and I'm very grateful for it) but I think the area needs some significant refactoring in the configuration and discovery parts. My biggest annoyance in there is that I go into a calendar and add a CalDAV server, and a collection, and then I go into tasks and add *the same* server, and *the same* collection, and then I go into Notes and add *the same server* and *the same collection* and then I go into the addressbook and add *the same server*, and (phew!) a different collection. There seems a little redundancy in that process, not least because for a given server I can discover all of a user's calendars and addressbooks, and whether they support calendar, tasks and/or notes by making two PROPFIND requests. Or maybe three requests, for a more recent server that allows discovery of the principal URL. Cheers, Andrew. -- http://andrew.mcmillan.net.nz/ Porirua, New Zealand Twitter: _karora Phone: +64(272)DEBIAN The real problem with hunting elephants is carrying the decoys. signature.asc Description: This is a digitally signed message part ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] e-d-s 2.32.0 error during make install
Ok, I have applied the patch I found here: https://bugzilla.gnome.org/show_bug.cgi?id=628238 but no luck, now I get that error: make[5]: Leaving directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal' make[4]: Leaving directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal' make[3]: Leaving directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal' Making install in libedata-cal make[3]: Entering directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' make install-am make[4]: Entering directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' make[5]: Entering directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' test -z "/usr/lib64" || /usr/bin/mkdir -p "/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64" /bin/sh ../../libtool --mode=install /usr/bin/ginstall -c -s libedata-cal-1.2.la '/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64' libtool: install: warning: relinking `libedata-cal-1.2.la' libtool: install: (cd /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal; /bin/sh /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/libtool --silent --tag CC --mode=relink gcc -O2 -fPIC -pipe -march=x86-64 -version-info 10:0:0 -Wl,--no-undefined -o libedata-cal-1.2.la -rpath /usr/lib64 libedata_cal_1_2_la-e-data-cal-enumtypes.lo libedata_cal_1_2_la-e-cal-backend.lo libedata_cal_1_2_la-e-cal-backend-cache.lo libedata_cal_1_2_la-e-cal-backend-factory.lo libedata_cal_1_2_la-e-cal-backend-intervaltree.lo libedata_cal_1_2_la-e-cal-backend-sexp.lo libedata_cal_1_2_la-e-cal-backend-sync.lo libedata_cal_1_2_la-e-cal-backend-util.lo libedata_cal_1_2_la-e-cal-backend-store.lo libedata_cal_1_2_la-e-cal-backend-file-store.lo libedata_cal_1_2_la-e-data-cal.lo libedata_cal_1_2_la-e-data-cal-view.lo ../../calendar/libegdbus/libegdbus-cal.la ../../calendar/libecal/libecal-1.2.la ../../libedataserver/libedataserver-1.2.la ../../libebackend/libebackend-1.2.la -pthread -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lical -licalss -licalvcal -lxml2 -lgconf-2 -lglib-2.0 -inst-prefix-dir /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1) .libs/libedata_cal_1_2_la-e-cal-backend-file-store.o: In function `e_cal_util_get_component_occur_times': e-cal-backend-file-store.c:(.text+0x170b): undefined reference to `e_cal_recur_ensure_end_dates' e-cal-backend-file-store.c:(.text+0x1946): undefined reference to `e_cal_recur_obtain_enddate' e-cal-backend-file-store.c:(.text+0x19cf): undefined reference to `e_cal_recur_obtain_enddate' collect2: ld returned 1 exit status libtool: install: error: relink `libedata-cal-1.2.la' with the above command before installing it make[5]: *** [install-libLTLIBRARIES] Error 1 make[5]: Leaving directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' make[4]: *** [install-am] Error 2 make[4]: Leaving directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' make[3]: *** [install] Error 2 make[3]: Leaving directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0' make: *** [install-strip] Error 2 Error! Configure exited with status: 2 Failed package evolution-data-server r...@quadser:/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG_2_32# Any ideas ? Rgds Saxa ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
Re: [Evolution-hackers] e-d-s 2.32.0 error during make install
Ok, now I'm on the list.
On Thu, Nov 11, 2010 at 3:56 PM, Sasa Ostrouska wrote:
> Hello, I get this error during make install phase:
>
>
>
> make[4]: Entering directory
> `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
> make[5]: Entering directory
> `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
> test -z "/usr/lib64" || /usr/bin/mkdir -p
> "/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64"
> /bin/sh ../../libtool --mode=install /usr/bin/ginstall -c -s
> libecal-1.2.la
> '/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64'
> libtool: install: warning: relinking `libecal-1.2.la'
> libtool: install: (cd
> /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal;
> /bin/sh
> /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/libtool
> --silent --tag CC --mode=relink gcc -O2 -fPIC -pipe -march=x86-64
> -version-info 10:2:2 -Wl,--no-undefined -o libecal-1.2.la -rpath
> /usr/lib64 libecal_1_2_la-e-cal-marshal.lo libecal_1_2_la-e-cal.lo
> libecal_1_2_la-e-cal-component.lo libecal_1_2_la-e-cal-recur.lo
> libecal_1_2_la-e-cal-time-util.lo
> libecal_1_2_la-e-cal-check-timezones.lo
> libecal_1_2_la-e-cal-system-timezone.lo libecal_1_2_la-e-cal-util.lo
> libecal_1_2_la-e-cal-view.lo ../../calendar/libegdbus/libegdbus-cal.la
> ../../libedataserver/libedataserver-1.2.la -pthread -lgio-2.0
> -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lical -licalss
> -licalvcal -lxml2 -lgconf-2 -lglib-2.0 -inst-prefix-dir
> /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1)
> libtool: install: /usr/bin/ginstall -c .libs/libecal-1.2.so.8.2.2T
> /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/libecal-1.2.so.8.2.2
> libtool: install: strip --strip-unneeded
> /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/libecal-1.2.so.8.2.2
> libtool: install: (cd
> /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64
> && { ln -s -f libecal-1.2.so.8.2.2 libecal-1.2.so.8 || { rm -f
> libecal-1.2.so.8 && ln -s libecal-1.2.so.8.2.2 libecal-1.2.so.8; }; })
> libtool: install: (cd
> /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64
> && { ln -s -f libecal-1.2.so.8.2.2 libecal-1.2.so || { rm -f
> libecal-1.2.so && ln -s libecal-1.2.so.8.2.2 libecal-1.2.so; }; })
> libtool: install: /usr/bin/ginstall -c .libs/libecal-1.2.lai
> /home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/libecal-1.2.la
> libtool: install: warning: remember to run `libtool --finish /usr/lib64'
> test -z "/usr/include/evolution-data-server-2.32/libecal" ||
> /usr/bin/mkdir -p
> "/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/include/evolution-data-server-2.32/libecal"
> /usr/bin/ginstall -c -m 644 e-cal.h e-cal-component.h e-cal-recur.h
> e-cal-time-util.h e-cal-check-timezones.h e-cal-system-timezone.h
> e-cal-types.h e-cal-util.h e-cal-view.h
> '/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/include/evolution-data-server-2.32/libecal'
> test -z "/usr/lib64/pkgconfig" || /usr/bin/mkdir -p
> "/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/pkgconfig"
> /usr/bin/ginstall -c -m 644 libecal-1.2.pc
> '/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/pkgconfig'
> make[5]: Leaving directory
> `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
> make[4]: Leaving directory
> `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
> make[3]: Leaving directory
> `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
> Making install in libedata-cal
> make[3]: Entering directory
> `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal'
> make install-am
> make[4]: Entering directory
> `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal'
> make[5]: Entering directory
> `/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal'
> test -z "/usr/lib64" || /usr/bin/mkdir -p
> "/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-
Re: [Evolution-hackers] e-d-s 2.32.0 error during make install
On Thu, 2010-11-11 at 15:56 +0100, Sasa Ostrouska wrote: > .libs/libedata_cal_1_2_la-e-cal-backend-file-store.o: In function > `e_cal_util_get_component_occur_times': > e-cal-backend-file-store.c:(.text+0x170b): undefined reference to > `e_cal_recur_ensure_end_dates' Search in the archives. A few days before oct 23. ___ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-hackers
[Evolution-hackers] e-d-s 2.32.0 error during make install
Hello, I get this error during make install phase:
make[4]: Entering directory
`/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
make[5]: Entering directory
`/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
test -z "/usr/lib64" || /usr/bin/mkdir -p
"/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64"
/bin/sh ../../libtool --mode=install /usr/bin/ginstall -c -s
libecal-1.2.la
'/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64'
libtool: install: warning: relinking `libecal-1.2.la'
libtool: install: (cd
/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal;
/bin/sh
/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/libtool
--silent --tag CC --mode=relink gcc -O2 -fPIC -pipe -march=x86-64
-version-info 10:2:2 -Wl,--no-undefined -o libecal-1.2.la -rpath
/usr/lib64 libecal_1_2_la-e-cal-marshal.lo libecal_1_2_la-e-cal.lo
libecal_1_2_la-e-cal-component.lo libecal_1_2_la-e-cal-recur.lo
libecal_1_2_la-e-cal-time-util.lo
libecal_1_2_la-e-cal-check-timezones.lo
libecal_1_2_la-e-cal-system-timezone.lo libecal_1_2_la-e-cal-util.lo
libecal_1_2_la-e-cal-view.lo ../../calendar/libegdbus/libegdbus-cal.la
../../libedataserver/libedataserver-1.2.la -pthread -lgio-2.0
-lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lical -licalss
-licalvcal -lxml2 -lgconf-2 -lglib-2.0 -inst-prefix-dir
/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1)
libtool: install: /usr/bin/ginstall -c .libs/libecal-1.2.so.8.2.2T
/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/libecal-1.2.so.8.2.2
libtool: install: strip --strip-unneeded
/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/libecal-1.2.so.8.2.2
libtool: install: (cd
/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64
&& { ln -s -f libecal-1.2.so.8.2.2 libecal-1.2.so.8 || { rm -f
libecal-1.2.so.8 && ln -s libecal-1.2.so.8.2.2 libecal-1.2.so.8; }; })
libtool: install: (cd
/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64
&& { ln -s -f libecal-1.2.so.8.2.2 libecal-1.2.so || { rm -f
libecal-1.2.so && ln -s libecal-1.2.so.8.2.2 libecal-1.2.so; }; })
libtool: install: /usr/bin/ginstall -c .libs/libecal-1.2.lai
/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/libecal-1.2.la
libtool: install: warning: remember to run `libtool --finish /usr/lib64'
test -z "/usr/include/evolution-data-server-2.32/libecal" ||
/usr/bin/mkdir -p
"/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/include/evolution-data-server-2.32/libecal"
/usr/bin/ginstall -c -m 644 e-cal.h e-cal-component.h e-cal-recur.h
e-cal-time-util.h e-cal-check-timezones.h e-cal-system-timezone.h
e-cal-types.h e-cal-util.h e-cal-view.h
'/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/include/evolution-data-server-2.32/libecal'
test -z "/usr/lib64/pkgconfig" || /usr/bin/mkdir -p
"/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/pkgconfig"
/usr/bin/ginstall -c -m 644 libecal-1.2.pc
'/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64/pkgconfig'
make[5]: Leaving directory
`/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
make[4]: Leaving directory
`/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
make[3]: Leaving directory
`/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libecal'
Making install in libedata-cal
make[3]: Entering directory
`/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal'
make install-am
make[4]: Entering directory
`/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal'
make[5]: Entering directory
`/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/WORK/evolution-data-server-2.32.0-1/evolution-data-server-2.32.0/calendar/libedata-cal'
test -z "/usr/lib64" || /usr/bin/mkdir -p
"/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64"
/bin/sh ../../libtool --mode=install /usr/bin/ginstall -c -s
libedata-cal-1.2.la
'/home/sasa/DEVELOPMENT/DROPLINE_GNOME/DBS/DLG/STAGE/evolution-data-server-2.32.0-1/usr/lib64'
libtool: install: warnin
Re: [Evolution-hackers] Rethinking account management
On Thu, 2010-11-11 at 08:55 +0100, Milan Crha wrote: > Will be there any kind of property inheritance? As in your example > above, I would like to define the 'color' in the [source] > key-file-group, thus all extensions will inherit it, but, if user > changes color for one of them, then it'll create its own key and it will > be used instead of the parent's. Certain keys can be inherited, yes. We've already seen inheritance in some examples I gave with the 'backend' key. Another example might be an 'enabled' key, which could work similar to widget visibility in that a child source may have enabled=true, but it's not -really- enabled unless all of its parent sources are also enabled. > Maybe it's not the best example with the color, but imagine the Exchange > account, I would like to define server address and credentials, > connection setup and such, in the parent, and the children > (mail/calendar/...) will inherit this. I imagine that too. I think groupware backends will have considerable freedom to distribute information across sources however they want. The API isn't nearly finished yet, but at the moment I'm thinking of embedding a GNode within each ESource object to represent the source's position in the hierarchy. The GNode's data value would point back to its ESource object, so you can access parent, sibling or child sources through the GNode API. For example, fetching account information from a parent source might look something like: /* Suppose ExchangeAccount wraps a GSettings object that * manages an [extensions/exchange-account] group in the * parent of a calendar source. The "exchange-account" * group holds the server address, credentials, etc. */ ExchangeAccount *account; ESource *parent; GNode *node; node = e_source_get_node (calendar_source); parent = E_SOURCE (node->parent->data); account = e_source_get_extension (parent, "exchange-account"); /* This retrieves the value of: * * [extensions/exchange-account] * hostname='my.exchange.server.com' */ hostname = exchange_account_get_hostname (account); > Imagine the exchange account again. Right now you define an account > name, and this name is used as a source group name in Calendar and such, > same as in mailer. With that you wrote I do not see a way of achieve > that just from the user's home. Or is this based on the existence of the > parent/backend key in the [source] key-file-group? In that case the > exchange account will have actually two files instead of one in the home > directory, one for group definition and one for real sources? It's > unnecessary, right? a) you would search for parents, in home and in > system directory. b) you should be able to easily distinguish between > group definitions and real sources definitions (all are named [source] > in your proposal) and be able to _easily_ reconstruct them. A groupware account will likely consist of a collection of key files, but you won't be interacting with key files directly, as shown above. Some central ESource registry will load all the key files, create an ESource object for each of them, arrange them in a hierarchy, and emit signals when the "sources" directory changes. > Also, remember that users can name their accounts whatever they want, > but not every latter is usable for the filename - so the files will be > either meaningless strings or something descriptive? Built-in sources can have meaningful UIDs like "on-this-computer" or "on-the-web", since those key files will be installed as part of the E-D-S package. User-created sources will use the same generated UID strings that we're using now, via e_uid_new(). > The last two questions (and I see I mostly answered above questions > myself), how will be the group definition propagated to mailer, > respectively how will be defined the POP account, which doesn't have a > group in the folder tree, same as the mbox, which is hacked in and > hidden in the background? Will these two kinds also require its own > group file (for the 'backend' key) or not? A pop account would look something like: [source] name='My POP Account' parent='on-this-computer' backend='pop' [extensions/mail] ... account details ... The folder tree will have to give special treatment to accounts that rely on the built-in local mail store, but we already do that. > Because you have [source] for groups and [source] for pseudo-sources > (the real source is at the [extension/...]), then will I be able to > define a child of the source, not of the group, and it'll be propagated > to the UI? Just an idea, not that I think it would be usable. I'm purposefully leaving the file format very open-ended and flexible. The API will be less so. There's all kinds of key file configurations you can think up that Evolution can't support right now. We can either decide it's an invalid configuration, or perhaps it could lead to a new feature. That's why I'm leaving it open-ended. Hopefully
