GNC-PRICES

[Paul Lussier]

In a message dated: 22 Feb 2001 16:38:14 CST
Rob Browning said:

>But this doesn't allow us any way to handle various versions of
>gnucash, unless we're going to have Bundle::GnuCash1.4,
>Bundle::GnuCash2.0 etc.
>
>I guess it still seems to me like the runtime dependencies should be
>indicated by whatever binary package you're installing, and the
>build-time dependencies should be handled by configure.in...

I guess I agree with that.  However, configure.in only allows you to determine 
whether everything required is actually in place already.

The Bundle::GnuCash allows you to make sure some of those requirements are 
in place prior to running ./configure.

I don't know how to solve the Bundle::GnuCash1.4 vs. Bundle::GnuCash2.0
issue.  Would  GnuCash1.4 work if Bundle::GnuCash2.0 were installed?
Or, better yet, make the configure.in for each rev require the appropriate 
bundle.  This can easily be accomplished using a VERSION var in the perl mod,
and making configure check for that.

I don't know if it's worth the effort or not, though.  The docs can just as 
easily list the perl mods required and you could leave it to the user to
exec:
	perl -MCPAN -e "install Mod1 Mod2 Mod3...."

So I guess it doesn't really matter.
-- 

Seeya,
Paul
----
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.

	 If you're not having fun, you're not doing it right!