From: Michel S. <Mic...@ep...> - 2004-10-04 20:28:10
|
Dear Fink developers, I'm currently trying to write a few packages for extensions for scsh (the Scheme Shell). To summarize quickly, scsh is a scripting language similar to Perl/Python/Ruby/etc. for which some libraries, which I'll call modules below, exist. I'd like to write Fink packages for these modules, and I have some questions related to that. To make the discussion which follows clearer, let me quickly explain how scsh modules are managed. First of all, in order to install scsh modules, one has to have at least scsh 0.6.6 installed, because some things are missing from earlier versions. There is a Fink package for scsh 0.6.6, so things are fine in that respect. Once scsh itself is installed, the module in charge of managing scsh modules, called "scsh-install-lib", has to be installed first. Finally, one can use the "scsh-install-lib" module to install further modules, written by the scsh community. I'm trying to write Fink packages for the "scsh-install-lib" module, and then for various existing modules, like "sunterlib", "sunet", and so on. The first problem I have is one of dependency. It happens that scsh modules are installed in directories which explicitly refer to the major and minor versions of scsh to which they belong, e.g.: <prefix>/share/scsh-0.6/modules/<module-name>/scheme ^^^^^^^^ where <prefix> is the prefix given at installation time (would be /sw for Fink) and <module-name> is the full name of the module, including its version. Since this directory (and the code it contains, in fact) is specific to scsh 0.6 and is not expected to work with scsh 0.7, I'd like to specify that in the "Depends" field. But I'd also like to specify that the version of scsh has to be greater or equal to 0.6.6, for the reasons given above. The following seems to work, but I wonder if there's a cleaner way: Depends: scsh (<< 0.7.0), scsh (>= 0.6.6) The other problem is one of naming. Since I expect that in the long run there will be quite a lot of Fink packages for scsh modules, maybe I should name them in some consistent fashion, or even put them in their own section. Any suggestion in that respect? Thanks, Michel. |