On Wed, 2012-07-25 at 12:28 +0200, Fotis Georgatos wrote: > Hi there, > >> > * Provide some smart way to handle dependencies like "tcsh" which have no > >> > meaning on Debian > > This is indeed a problem, we added detection for debian packages with > > dpkg in the develop branch now. But since packages across distro's can > > have different names this is no perfect solution. > > Exactly. eg. let's keep in mind -devel (RH way) & -deb (Debian way). > As expected, there are quite a few of them. > > I think the OS-distro-backend should be tunable. If you'd like to write > together the "HPC-RFC 0002" about how to manage this, count me in. > This will give you ideas about how best to proceed: > http://www.ccac.hpc.mil/consolidated/bc/policy.php # eg. look FY05-06/FY06-19 > (ie. a good implementation should provide a solution even for gentoo et al!) > > > A way to solve this would be by just adding a .eb file for tcsh > > Yeap, that's what might be the best workaround for now.
We're just adding proper support for 'sanityCheckCommand' in the develop branch this week. This got me thinking about creating an .eb file without any sources, but provide the 'sanityCheckCommand="tcsh --version"', this way nothing will be actually build, but you will still have a failure of creating the module file if tcsh is not installed on the system. But this would create to much clutter of 'fake/dummy' modules, so maybe replacing osdependencies with a 'prerequisites_commands', which contains a list of commands that shouldn't fail for this module to actually build would be a better option? Jens Timmerman
