| |||||||||||||
|
| |||||||||||||
DependenciesDependenciesPosted Dec 5, 2002 4:46 UTC (Thu) by torsten (guest, #4137)Parent article: Coming soon: gnucash 1.8 Last I read, installing GNUcash meant dependency hell - mostly because of many, varied, necessary libraries that must be installed. I would have preferred mention of these. I run a minimum system, I don't like to have extra crap lying around. Knowing how much goes into using this package would be helpful.
(Log in to post comments)
Dependencies Posted Dec 5, 2002 9:01 UTC (Thu) by aglet (guest, #1334) [Link] "Dependency hell" as you call it could also be called modularity and code re-use... the fact that you don't actually have anything else that also uses GNUcash's dependencies is perhaps a shame, but is your disk space really that precious? It is a heavyweight desktop application, after all, not some embedded application.If managing the dependencies is a problem, take it up with your distribution vendor -- most modern distributions have some mechanism (eg up2date, apt-get dist-upgrade) for dealing with it... Would you rather have a giant opaque GNUcash package containing specific versions of the libraries it uses?
Dependencies Posted Dec 5, 2002 9:16 UTC (Thu) by ekj (subscriber, #1524) [Link] It *is* a problem. Case in point. I had Mandrake 8.1 and wanted to run the newest gnucash, this was when my distro was maybe 5 months old or so.urpmi gnucash* Complained that it needed to upgrade ~25 libraries, about 5 of which urpmi knew of no source for. No problem I said, go ahead. But then it turned out that this would break many of my older applications, so they would *also* need to be upgraded. In principle it should be possible to have two different versions of the same lib, in practice this works sometimes, and othertimes not. So, to run this one program I would have been forced to:
This is not a reasonable amount of effort to put into installing a single program. What it means in practice is that I, and probably very many others, have completely given up on trying out new betas and CVS-versions and suchlike of Gnucash, and instead stick with the version that comes in our distro and "just works". This is a pity, because it reduces the amount of testing a new version gets before it becomes the official one.
Dependencies Posted Dec 5, 2002 9:59 UTC (Thu) by aglet (guest, #1334) [Link] Ah, but beta testing is different to just wanting to run the application (which is what I nuderstood the previous poster to be saying). Perhaps you should keep a small "bleeding edge" partition if you can't manage to keep your stable stuff working as well as running recent betas? Maybe a switch in distribution would help -- I drag in a few packages from the Debian unstable & testing distributions into my stable laptop, it seems to work fine...
Dependencies Posted Dec 5, 2002 12:04 UTC (Thu) by ranger (guest, #6415) [Link] Debain isn't the only distro out there of course. There's no need to switch distros, upgrading to Mandrake 9.0 should be sufficient, at most the user could add a cooker source to urpmi to install the required libraries (and remove it afterwards, to prevent getting a whole bunch of other possibly semi-broken software).But, installing the deps on a pre-Gnome2 distro to be able to run a development version of GTK/Gnome software is probably not feasible, at least not without requiring upgrades on much of the software (since many of the dependencies are complex, to allow gnome1.x software to co-exist with Gnome2 may require upgrading Gnome1.x libraries, requiring software depending on those libraries to be upgraded also). Why doesn't one see this with KDE though, I wonder ...
Dependencies Posted Dec 11, 2002 23:22 UTC (Wed) by Wilddev (guest, #8514) [Link] I'm not quite sure what you're implying here, but GnuCash 1.8.0 is a GNOME 1.4 application and doesn't require any GNOME2 libraries. Also as someone actively involved in GNOME I know that GNOME 1.4 and GNOME2 happily co-exist allowing you to run applications developed for either platform as required.
Dependencies Posted Dec 11, 2002 23:18 UTC (Wed) by Wilddev (guest, #8514) [Link] I'd like to point out that mdk 8.1 _comes_ with GnuCash 1.6.2. The only dependency problems you should encounter with the new version of GnuCash over the one supplied as part of mdk 8.1 is an upgraded g-wrap library. There is no 25 library upgrade problem. If, however, you are running KDE as your desktop, then of course as GnuCash has currently only a GNOME 1.4 based front end you will need to install enough of GNOME to run it. (a KDE developer has recently started working on a KDE based interface for the GnuCash engine incidentally).There is quite a bit of misinformation about GnuCash's requirements out there. GnuCash is no more difficult to install with GNOME 1.4 already installed than any of the other GNOME Office applications (Gnumeric, Evolution, Abiword, etc).
Dependencies Posted Dec 18, 2002 17:54 UTC (Wed) by dbreakey (guest, #1381) [Link] This is not a library issue, but a packaging issue; unfortunately, I don't think that anyone has come up with a reasonable, usable solution for this. Consider the following:
Therefore, in order to continue producing a distribution that meets their desired level of quality (whatever that might be), most vendors only spend their time testing and validating the latest—or at least whatever point on the curve they want to be at; some vendors prefer to hang back a bit from the absolute latest sutff, while others like to live on the bleeding edge—releases of any given application. The downside to this is that users, in order to upgrade to the latest version of one particular application, may be required to upgrade a large portion of their system in order to satisfy dependancies—dependancies which are determined by the vendor and hard-coded into the package information. If you don't want to do this, you may want to start using one of the increasing number of "build from source" distributions, which will probably give you far more control over the exact content of your system.
|
|
||||||||||||