Attached is hercules-2.17.1.ebuild. This is an update to the newest version of hercules (from 2.16.5, which was submitted 3 months ago (bug 13237) but has not yet made it into portage - hercules-2.15.ebuild is currently the latest version in portage). This replaces previous versions. Also the file files/hercules.cnf is no longer needed. Hercules is an IBM System 360/370/390 and Z/Server emulator which runs and compiles under Linux and Windows operating systems and is available in several Linux distributions (Suse, Debian etc). Using this package you can run IBM (and other vendors) mainframe software on your PC such as MVS, VM, VSE, Linux for S/390 and Linux for zSeries. For more information see http://www.conmicro.cx/hercules
Created attachment 8883 [details] hercules-2.17.1.ebuild
*** Bug 13237 has been marked as a duplicate of this bug. ***
Noticed that this was added to portage. Thanks. Wondering why the keywords for PPC, SPARC and ALPHA were removed. Hercules is known to compile and run on all of these architectures. ?? Also, what is the criteria for masking? ie: how long until the ~x86 keyword is changed to x86?
Hmmm. On closer examination it seems that hercules-2.17.1.ebuild was copied from hercules 2.1.5.ebuild. Can you please replace this with the attachment provided. (this explains the missing keywords and other changes not reflected in the committed ebuild). This kind of shortcut could lead to problems in a more complex package.
If hercules.cnf is no longer needed, why does the provided ebuild still install it?
Sorry. I didnt express myself too well. hercules.cnf is still required by the package (it is a sample configuration file) but the seperate copy which I had attached to be placed in the files dir origianlly (in the 2.15 ebuild) is not required as it is now being taken from the hercules distribution tarball. To be honest I cannot recall exactly why I did it that way in 2.15, however the 2.17 ebuild uses the distributed hercules.cnf file as the sample. Yet another thing I was hoping to correct with the submitted 2.17 ebuild.
I see. Nothing changed wrt to how the config file is installed compared to the existing 2.17.1 ebuild. After cleaning up your ebuild a bit, the changes it has are: - different way to setup CFLAGS (really necessary?) - support for other archs - less picky about what to install from the html/ subdir (I need to verify that this is correct). - a little more documentation printed. I changed ./configure back to econf, and make to emake. These are needed to support distcc, which a lot of ppl use. If hercules blows up with parallel make, we'll need to revert this... but most likely it'll work just fine. I'll check in the -r1 ebuild after a little more testing... let me know if it works for you.
New ebuild checked in.
