I was hoping somebody qith some experience could create a mercury ebuild. If nobody does, I will try, but since I am quite the n00b to linux it will probably suck.
Created attachment 80256 [details] mercury-compiler-0.12.2.ebuild I've got a basic ebuild for mercury (attached) but it runs into numerous "sandbox violations" during the install procedure. This means that to install it, you need to disable the sandbox safety features like so: >> FEATURES="-sandbox" emerge mercury-compiler I'm sure this is not Gentoo recommended practise, but it will get you a portage-managed mercury environment. Of course, the ebuild will never be added to portage in this state. I dont know whether there is a standard way to address these problems, or whether the mercury team would need to adjust their build environment before we can make it work. But, if anyone has suggestions on how to fix this, I work in the same department as many of the core mercury developers so I'd be happy to pass suggestions/queries to them. By the way, for those unfamiliar with Mercury, the project website is: http://www.cs.mu.oz.au/research/mercury/ Cheers, Ryan
Ryan, thanks for the ebuild. A few comments: - (a minor quibble) - it's perhaps preferable to rename the package to mercury-0.12. - you don't need to inherit the eutils eclass unless you're going to use it. - you have mono in IUSE, yet don't refer to this anywhere in the ebuild. Is this for the .dotnet grade? - is version 1.4 of virtual/jdk required when USE="java", or is it possible for a user to use the java grade with >=jdk-1.2? - upstream's build methodology looks sane; the sandbox errors should be able to be resolved by passing ${INSTALL_PREFIX} to make install. Note: you'll also need to set ${MERCURY_COMPILER} to the file 'mercury_compile' that will be sitting in ${D}. - man pages should be installed into "${D}"/usr/share/man; info pages should be installed into "${D}"/usr/share/info. These locations can be set via ${INSTALL_MAN_DIR} and ${INSTALL_INFO_DIR}. - there are a few extra READMEs and other plain text docs that should be installed.
- point one should read "...rename the package to mercury-0.12.2" :)
Two more issues to consider for a mercury ebuild: - A vanilla build will not bail out on a compile failure. The toplevel Makefile will need to be patched in order to do this. - The java grade will not compile; there is no type definition for pseudo_type_desc in library/type_desc.m
Assigning this bug to myself. mercury is a fantastic language and will make a fine addition to dev-lang. :)
mercury-0.12.2 has been committed to cvs. It contains a few patches that resolve the following issues: - mgnuc will now respect ${CFLAGS} when compiling source files - 'mmake all' and 'mmake install' will bail out on errors - dvi docs are not installed
