In <20090525163904.gb5...@cat.rubenette.is-a-geek.com>, lee wrote: >On Sun, May 24, 2009 at 03:28:50PM -0500, Boyd Stephen Smith Jr. wrote: >> In <20090524145214.ga16...@cat.rubenette.is-a-geek.com>, lee wrote: >> >I >> >don't want to run an akonadi server either, whatever that is. >> Oh, then you don't want to run those parts of KDE; They require a >> connection to an Akonadi server. They've been scheduled to since before >> KDE 4.0 was available. >Maybe not. I'd be fine without them, if it would work without --- but >it doesn't.
I said it before, and I'll say it again: That is just not true. I was careful in my package selection and I have a working KDE 4.2 (including my must-have kmail) and I do not have a mysql server installed. KDE 4.2 can work without Akonadi, with a minimum of fuss. >> Not if the file format was public. I can understanding not using a format >> that can't be processed without a particular piece of software, but the >> on- disk format used by MySQL is public information. You don't have to >> use MySQL to access. You can write your own software or pay someone to >> write the software for you without the blessing or control of MySQL. >Where do you find the needed information in 20 years? On your HD, or wherever you chose to store it. If the information is public you can copy it to any location and translate it to any form you need to. >And what if you >want to access the stored information but you don't want to wait a >year or two before you were eventually able to figure out what format >was used to store it and to create software allowing you to retrieve >the information? Use the old software. It might not run on the latest release of Debian, but it should run on whatever version you had before. Older releases are maintained in the archive, and you can archive whatever you need yourself if you don't want to depend on the Debian infrastructure. No one is forced to upgrade, but support does dwindle for a product over time. >And BTW, it's not only wasting resources to have a mysql server >installed that you don't need and don't use, it's also about making >things more complicated and time consuming when you have a mysql >server that eventually needs to be adminstered and that you eventually >have to figure out a way to make backups for? IIRC, Akonadi uses the "embeded" MySQL by default. It stores data and settings in your $HOME so it would be naturally included in any backup. It also is fully administered by the Akonadi server itself. >What if you use >stable and from one distribution to another, or the one after the >next, they change something about mysql and you suddenly find yourself >with the problem of having to somehow convert your data to be able to >use it with the new mysql version? Data translation issues can, have, and will happen even if "plain text" files. KDE generally hides this from the user. For example, the KDE configuration API allows the developer to register a translation that is required (maybe something simple like a configuration key rename) and what translations it depends on. The configuration file will contain a list of the translations already applied to it and the API will "automatically" apply whatever is needed to update the file. These same issues can be hidden when using RDBMS backed, but the translations are usually much faster. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
signature.asc
Description: This is a digitally signed message part.
