I have a package (duplicity) that for some reason did not get moved to the 10.8 
tree.  I have updated the package and it builds on Mac OS X 10.8, 10.6 and 10.5.

The package is dependent on python.  The minimum requirement is python 2.4 and 
has been tested up to python 2.7.  What is the best route
        A. Require python 2.7 in the dependencies since it is available in all 
systems as a build
        B. Let the user chose by creating a duplicity-py24, duplicity-py25, 
duplicity-py26 and duplicity-py27
        C. Other, is there a method for creating a dependence on "python (>= 
2.4)" ??

I have created the updated version based on A but that forces a large install 
for many users.  Option B seems more user interaction than is necessary for 
such a package.  C would be fine but I haven't seen that used in any other 
package and not sure it is legal.  Also there is a dependence on boto-py27 
which is explicit.  My current depends are:
# Dependencies.
BuildDepends: librsync (>= 0.9.7-1002), fink (>= 0.24.12-1)
Depends: python27, librsync-shlibs (>= 0.9.7-1002), ncftp, lftp, boto-py27

There are cases where a user would want python 2.6 or greater since it allows 
multiprocessing some of the data transfers but is there a better way to make 
the package use already installed or system versions of python?

Secondly, the fink web site seems to be down so where do I submit packages?

Thanks,
Scott



------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to