LWN.net Logo

why not solve the dep. problem once ?

why not solve the dep. problem once ?

Posted Aug 12, 2003 10:31 UTC (Tue) by guybar (guest, #798)
In reply to: State of the GnuCash project by stevep
Parent article: State of the GnuCash project

Whoa, that's a lot of design changes just b/c of release constraints !

why not, instead:

1) create a single directory-tree including _ALL_ the libraries and tools that gnucash needs, for the current dev. version., in binary form.
plus, perhaps, a small scriptlet to source for the environment vars.

2) tar bzip the tree.

3) repeat 1-2 for the latest versions of 4 major distribs (RH, SUSE, MDK, DEB testing or unstable)

4) repeat 1-3 for each new gnucash dev. version.

release as a sort of "permanent alpha/beta" status package. (i.e. for devs only)


In other words, I view the compilation problems as more of a distribution difficulty (as in distributing to the client, not as in lin. dist.) than as a design defect. The solution should be in that direction.


(Log in to post comments)

why not solve the dep. problem once ?

Posted Aug 12, 2003 12:59 UTC (Tue) by kleptog (subscriber, #1183) [Link]

You don't need to do it for Debian. apt-get install gnucash has always worked for me. I'm upgrading from 1.6 to 1.8 right now. Sure, apt needed to upgrade 13 other packages, but hey. I don't have to think about!

Thank god for Debian.

URPMI's the same

Posted Aug 12, 2003 14:35 UTC (Tue) by leonbrooks (guest, #1494) [Link]

"urpmi --auto-select" gets latest versions and all necessary dependencies plus
knock-on dependencies.

Copyright © 2012, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds