kMyMoney2 and KDE4

Message

Mark Clegg · Post by **Mark Clegg** » Sun Nov 08, 2009 12:36 pm

Now that KDE3 support has been deprecated, what options are there for us kMyMoney users, which as far as I can tell, still only supports KDE3?

I'm running KDE4, and an quite happy with it, and the only things that have been keeping bits of kde3 on my system have be k3b and kmymoney

As k3b for kde4 is now marked stable (although still alpha), that just leaves kMyMoney.

Will I have to add the kde3 overlay to keep my kde3libs intact, or does anybody know when kmymoney2 will be kde-4'd ?

Alternatively, is there any alternative to kmymoney2 for kde4 that can import the kmymoney datafiles?

mcuddy · Post by **mcuddy** » Wed Nov 25, 2009 4:44 pm

Please help!!! I need a way to keep Kmymoney running smothly - I use it for all of my finances. I stupidly unemerged kdelibs3.5 and now it looks like my kmymoney is going to go... What do I do? (I don't really like the option of switching to another linux - I like gentoo...

Ahenobarbi · Post by **Ahenobarbi** » Wed Nov 25, 2009 5:11 pm

emerge -av autounmask and get kde3.5 stuff back. Learn how to use overlays http://www.gentoo.org/proj/en/overlays/userguide.xml - kde3 stuff ( including KMyMoney) will be removed from portage

guimera · Post by **guimera** » Fri Nov 27, 2009 8:24 pm

Same problem here--I cannot live without Kmymoney and I cannot afford waiting for their awesome team to port it to KDE4.

The cleanest solution, I think, is to add the kde-sunset overlay, which, if I understand correctly, is where KDE3 will be left to die peacefully (as opposed to the euthanasia in the main tree). To add the kde-sunset overlay follow section 1 of this howto.

Now you have kmymoney in the kde-sunset tree, so you are ready for its removal from the main tree. Until that happens, you may want/need to unmask kmymoney (so that emerge doesn't complain):

Code: Select all

emerge -av autounmask
autounmask app-office/kmymoney2-1.0.2

And I think that's it. Am I right?

Mark Clegg · Post by **Mark Clegg** » Sat Nov 28, 2009 9:32 am

I'm currently thinking, that because kmymoney2 is in my world file, an emerge --depclean won't remove it, and also, because the required kde3.5 libs are dependencies, they won't get removed either.

So

If I do nothing, kmymody2 and required kde3.5 bits won't actually get uninstalled, they'll just disappear from portage and become unmaintained.

Then when a kde4 port of kmymoney comes along, they'll just get automatically upgraded and the old versions removed.

Alternatively, I could go with the sunrise overlay, but I'm not sure there's an actual requirement to do this.

Can somebody correct me if I'm wrong...

SamuliSuominen · Post by **SamuliSuominen** » Sat Nov 28, 2009 1:33 pm

Might want to try out out app-office/skrooge?

guimera · Post by **guimera** » Sat Nov 28, 2009 6:19 pm

Mark Clegg wrote:I'm currently thinking, that because kmymoney2 is in my world file, an emerge --depclean won't remove it, and also, because the required kde3.5 libs are dependencies, they won't get removed either.

So

If I do nothing, kmymody2 and required kde3.5 bits won't actually get uninstalled, they'll just disappear from portage and become unmaintained.

Then when a kde4 port of kmymoney comes along, they'll just get automatically upgraded and the old versions removed.

Alternatively, I could go with the sunrise overlay, but I'm not sure there's an actual requirement to do this.

Can somebody correct me if I'm wrong...

I see some problems with the "do nothing" approach. The most significant problem is that, I think, once kmymoney2 is removed from the main tree, all its kde3.5 dependencies (all its dependencies, for that matter) will be removed by "emerge --depclean" (unless those dependencies are removed from the main tree at the exact same time as kmymoney2--which I don't think is the case--or unless you have some other outdated kde3 package with the exact same dependencies--but such a package will eventually be removed just like kmymoney).

Another problem is that once kmymoney is removed from the tree you are on your own--if you want to uninstall it, for example, you will have to go and fetch all the files by hand. The last advantage I see to the overlay approach is that if, let's say, a bug is discovered in kmymoney or its dependencies, you will be stuck with that bug, whereas the overlay may still be updated (if not as frequently as the main tree).

In short, if you don't use the overlay, you have all the headaches of dealing with a complicated piece of code (complicated because of all its KDE dependencies) without portage.

BTW, I just checked Skrooge--it looks great! How come it does not come up in the first page of a Google search of "KDE personal finance" or "KDE accounting"?!??!

Mark Clegg · Post by **Mark Clegg** » Sat Nov 28, 2009 8:16 pm

guimera wrote:I see some problems with the "do nothing" approach. The most significant problem is that, I think, once kmymoney2 is removed from the main tree, all its kde3.5 dependencies (all its dependencies, for that matter) will be removed by "emerge --depclean" (unless those dependencies are removed from the main tree at the exact same time as kmymoney2--which I don't think is the case--or unless you have some other outdated kde3 package with the exact same dependencies--but such a package will eventually be removed just like kmymoney).

I'm not sure that's right. Because kmymoney2 is already merged, it's ebuild is cached in /var/db/pkg/app-office/kmymoney2-1.0.2, along with a record of it's dependencies and installed files. So even if it disappears out of the tree, the local copy of portage still knows everything it needs to know about it, and should therefore honour it. (I note it's now package masked to stop new installs, and an emerge -uavDN world complains about it). I don't think it or any of it's dependencies, however, will be removed, because a --depclean only removes un-needed packages, and kmymoney2 is still in the world file. Time will obviously tell...

I do agree that without the overlay I'm on my own, but an emerge -C followed by a depclean should still work properly I ever want to remove it.

in the meantime... time to go look at skrooge.....

jsn · Post by **jsn** » Sun Nov 29, 2009 3:00 pm

Good news for KMyMoney users:

"The development team has made the decision to release a beta on December 28th..." read rest from:
http://soliverez.com.ar/drupal/node/134

mcuddy · Post by **mcuddy** » Mon Nov 30, 2009 1:05 am

The overlay installed without a hitch... I hope it works

Also, I am hopeful the KMyMoney4 becomes stable soon.

Xywa · Post by **Xywa** » Mon Dec 07, 2009 9:40 am

jsn wrote:Good news for KMyMoney users:

"The development team has made the decision to release a beta on December 28th..." read rest from:
http://soliverez.com.ar/drupal/node/134

I hope everthing will be OK, as mcuddy said - I use it for all of my finances.

Might want to try out out app-office/skrooge?

It possible to move data form kmymoney2 (which is perfect) into skrooge?

Xywa · Post by **Xywa** » Thu Jan 07, 2010 11:26 am

jsn wrote:Good news for KMyMoney users:

"The development team has made the decision to release a beta on December 28th..." read rest from:
http://soliverez.com.ar/drupal/node/134

There is the 7th of January 2010 and there is still no Kmymoney in Gentoo

Any news about that?

SamuliSuominen · Post by **SamuliSuominen** » Thu Jan 07, 2010 11:43 am

Xywa wrote: There is the 7th of January 2010 and there is still no Kmymoney in Gentoo
Any news about that?

http://bugs.gentoo.org/show_bug.cgi?id=294010

I've been working on it indirectly by bumping aqbanking, and friends to Qt4 versions.. so everything it needs is in shape.. just haven't got to the application itself yet

SamuliSuominen · Post by **SamuliSuominen** » Thu Jan 07, 2010 7:57 pm

I'm afraid 3.95.0 doesn't seem very usable version and we have to wait until next alpha. See,

http://bugs.gentoo.org/show_bug.cgi?id=294010#c7

EDIT: It's now in Portage.

pilla · Post by **pilla** » Mon Jan 11, 2010 5:24 pm

Moved from Other Things Gentoo to Desktop Environments.

As for skrooge, I've tried to use it a couple times and it has frozen before I could add more than a couple accounts. Besides, there is no easy migration from kmymoney to skrooge for now.

wdsci · Post by **wdsci** » Thu Jan 14, 2010 6:22 am

For what it's worth, I've installed KMyMoney 3.95 and it's been working fine for me. Not to say that nobody else has problems with it, this is just my experience, but I would suggest to fans of the program that the 3.95 version currently in Portage is worth a try.

I'm still keeping the old KDE3 version around for a while in case something goes catastrophically wrong.

Gooserider · Post by **Gooserider** » Wed Jan 20, 2010 7:19 am

I see that KMyMoney is still masked as unstable for X86 (it would be REALLY NICE if there was an easy way to find out why...) and this thread really doesn't seem to make it clear on whether or not it will work on a system that has been downgraded from KDE3.5.10 to KDE4.3.3...

Is the current unstable mask there for a definite reason, or is it just waiting to see if there are any complaints filed?

I'm looking for a package to do investment tracking, primarily stocks and possibly options - and it looks like KMyMoney would do that, and I haven't seen anything else that appears like it would work and be relatively modern... GnuCash looks like it might as well, but since KDE is my native desktop environment, I'd rather not drag in all the Gnome Kruft...

Is it functional to emerge KMyMoney 3.95 on a KDE 4.3.3 system?

Are there any USE flags or other stuff that I also need to get in order to be able to do stuff like getting stock quotes and so forth?

Are there any other alternatives that might be better for stock portfolio management (the other stuff is not critical to me...)

Thanks,
Gooserider

pilla · Post by **pilla** » Wed Jan 20, 2010 12:16 pm

The discussion about packages being masked and when they would be unmasked is a recurrent theme. As for KDE, 3.9x packages are usually deemed betas by upstream, so I don't expect it to be unmasked, ever.

SamuliSuominen · Post by **SamuliSuominen** » Fri Jan 22, 2010 4:13 pm

pilla wrote:The discussion about packages being masked and when they would be unmasked is a recurrent theme. As for KDE, 3.9x packages are usually deemed betas by upstream, so I don't expect it to be unmasked, ever.

Correct. 3.95.0 won't ever go stable, a future 4.0.0 might

Gooserider · Post by **Gooserider** » Fri Jan 22, 2010 11:25 pm

Thanks... I have now installed the stable version of GnuCash instead - not thrilled about using a GNOME product in a KDE environment, but it does appear to be working OK and it's stable - long as it doesn't give me Mono...

My complaint wasn't so much about whether or not a package would be going stable (Though that would be nice to know) as the seemingly difficult problem of finding out WHY when emerge says a package is masked, and following from that whether or not it would be safe / wise to unmask it for my system... I may be missing an easier method, but as best I've been able to tell, the process goes something like:

Code: Select all

emerge -s kmymoney
Searching...
[ Results for search key : kmymoney ]
[ Applications found : 1 ]

*  app-office/kmymoney [ Masked ]
      Latest version available: 3.95.0
      Latest version installed: [ Not Installed ]
      Size of files: 13,881 kB
      Homepage:      http://sourceforge.net/projects/kmymoney2/
      Description:   A personal finance manager for KDE
      License:       GPL-2

So go to http://packages.gentoo.org/ and try to deal with it's really clunky interface (any reason they can't have a simple SEARCH function?) to find the package, at which point you can find out whether it is "hard masked" or "unstable" - which is good as far as it goes, but there doesn't seem to be any way to tell from there WHY it's "unstable"...

- is it because the package isn't being maintained, but seems to work?
- is it because the package is still being tested to see if everything is OK before going stable?
- is it because upstream said its a beta / not stable?
- is it because of a reported bug?
- is it because it really IS "unstable"

There does not seem to be a clear way to find this out, and it seems to me that this is the kind of information I'd want to know in order to decide whether I want to unmask the package for my system... There is a big difference between "it should work, but we aren't certain yet" and "yes it's there, but you really shouldn't..." and the current tools don't make it easy to find out which it is...

If there was an easily findable comment on the file that said WHY the file is unstable - in this case, something like "package considered Beta by upstream, unlikely to go stable" it would have been really helpful.

Gooserider

wdsci · Post by **wdsci** » Sun Jan 24, 2010 6:45 pm

You might want to install app-portage/eix, which is an optimized Portage search tool that (among other features) uses colors to distinguish the various sorts of masked packages - red for hardmasked, orange for unstable, green for stable. Additionally, for manually hardmasked packages, if you run "emerge -p <packagename>" it will give you an error message that includes the reason the package was masked. Alternatively, the messages come from /usr/portage/profile/package.mask so you could just grep that file for the package in question.

For what it's worth, I've been using KMyMoney 3.95.0 for a couple of weeks now (on KDE 4.3.4) with no problems. I believe it's marked unstable simply because it's a beta version of KMyMoney 4 (a version number like 3.95 usually indicates an alpha/beta for the next major version). It's been doing well enough that I'm confident in removing the old KDE3 version of KMM (though I am keeping regular backups of the ledger file, just in case). Since you seem to be rather attached to KMyMoney, I'd suggest unmasking it in package.keywords and trying it out. The worst that can happen is that it doesn't work, and then you can just uninstall it and wait for the stable version.

SamuliSuominen · Post by **SamuliSuominen** » Sun Jan 24, 2010 6:56 pm

By the way, there will be new AqBanking and KMyMoney releases (3.96) inside next 3 weeks. This is a fact from upstream maintainers

Xywa · Post by **Xywa** » Mon Jan 25, 2010 1:57 pm

I have small problem with kmymoney under kde4:
http://img202.imageshack.us/img202/7196/kmymoney.jpg

I can't change the size of the window with kmymoney, and the window is to too big and behind the menu bar (have a look on the picture above).
Any idea how to fix it?

pilla · Post by **pilla** » Mon Jan 25, 2010 3:18 pm

Xywa wrote:I have small problem with kmymoney under kde4:
http://img202.imageshack.us/img202/7196/kmymoney.jpg

I can't change the size of the window with kmymoney, and the window is to too big and behind the menu bar (have a look on the picture above).
Any idea how to fix it?

Alt+left button may help you moving the window around (I am using openbox right now, but maybe KDE uses the same shortcut).

Gooserider · Post by **Gooserider** » Mon Jan 25, 2010 9:31 pm

Xywa wrote:I have small problem with kmymoney under kde4:
http://img202.imageshack.us/img202/7196/kmymoney.jpg

I can't change the size of the window with kmymoney, and the window is to too big and behind the menu bar (have a look on the picture above).
Any idea how to fix it?

Play with the configuration on the menubar? I put mine on the bottom of my screen, and set it to autohide unless I put my mouse cursor on the bottom edge of the screen. Only time it's a minor nuisance is when I'm using Konsole, with multiple windows open - I have to be careful to "sneak up" on the tab bar to switch windows, and not go low enough to pop up the menu bar. I'm sure I could fix that if I really tried but...

Gooserider

kMyMoney2 and KDE4

kMyMoney2 and KDE4

Seriously - All my finances are on Kmoney