[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Systemusers as Addressbook resource
From:       "Friedrich W. H. Kossebau" <Friedrich.W.H () kossebau ! de>
Date:       2005-07-11 13:36:19
Message-ID: 200507111536.19510.Friedrich.W.H () kossebau ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Am Montag, 11. Juli 2005 14:06, schrieb Reinhold Kainhofer:
> On Monday 11 July 2005 14:00, Tobias Koenig wrote:
> > On Sun, Jul 10, 2005 at 04:38:12PM +0200, Friedrich W. H. Kossebau wrote:
> > > Hello,
> >
> > Hi Friedrich,
> >
> > > How could this be achieved? For one I wonder why noone seems to have
> > > ever thought of using one of the first of all addressbooks in the unix
> > > world, the entries in passwd (and .plan & .project)?
> >
> > There was such an resource somewhere in CVS already, but I can't remeber
> > where, so I guess it's also outdated ;)
>
> Ian Geiser started something like that, no idea how far he worked on it or
> if it is even available somewhere. You might contct him directly.

Will do :)

> > > But does the KAddressbook system support mapping? What if one
> > > has some other user already in his private addressbook? How could
> > > additional contact information not delivered by the system be stored?
> >
> > This issue will be solved in KDE 4.0, for KDE 3.5 we should use a
> > read-only resource.
>
> The only problem I see is that you'll possibly have lots of duplicates in
> the addressbook (okay, that alreay happens with the svn accounts and the
> pim developer resource anyway).

If the duplicates are due to the same LDAP resources serving system users and 
address book entities this should be solvable some way by fiddling with the 
resources.

Regards
Friedrich

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]