I have created an ebuild for the GRASS GIS project, an Open-Source Geographic Information System. Since it has an extensive set of dependencies, I thought others might benefit from an ebuild. This ebuild has been tested on 2 different Gentoo 1.4 systems and seems to build correctly (from /usr/local/portage/app-misc/grass/). I am still working on an ebuild for a separate add-on component called 'gdal' (Geospatial Data Abstraction Library) and will submit that and an update to the grass ebuild when ready. I am completely new to the GRASS package, so questions regarding its use should be referred to the GRASS homepage. Thanks Reproducible: Always Steps to Reproduce:
Created attachment 9669 [details] Ebuild for GRASS 5.0.1
Created attachment 9670 [details] 'Changelog' file for GRASS 5.0.1 ebuild
Created attachment 9671 [details] 'digest' file for GRASS 5.0.1 ebuild
Ok, sorry for the delay, I've been trying unsuccessfully to avoid a social life, what can I say. A few notes about the ebuild, though: 1) All the comments in skel.ebuild (other than the header) can be nuked, there's no reason to leave them, and they tend to slow down modem users like myself :) 2) IUSE should only contain USE flags that the ebuild makes decisions based on. That means that anything in IUSE should appear either as 'foo?' or 'use foo' somewhere in the ebuild 3) This package has a lot of dependencies. If some of those are optional, and a relevant use flag exists, you should make the features depend on the use flags, and then make sure they get into IUSE. In my opinion, the best source of info on such voodoo is `man 5 ebuild` 4) You don't need to go through the trouble of submitting a ChangeLog or digest, as it's usually fairly easy for the dev to auto-generate those, and we have good policies on giving the people that submitted the build credit in the changelog :) On a side note, instead of a big long ./configure line, econf can take extra arguments, so try something like this: econf --option-one \ --option-two That way, you don't have to have the initial cruft like --host=${CHOST} On another side note, in src_install, if you don't need extra parameters, just use emake. If you'd like to touch this up and post it again, that'd be great, and once that's done I'll try to get it into the tree promptly. Thanks for contributing (there's way more work than devs), and please continue to do so. Graham
I actually wrote my own grass 5.0.1 ebuild before I saw this thread. I've merged the better parts of the ebuild posted here by Andy with mine, and I'm just giving it a run-thru before I post it. I'm trying to determine the best way to handle the many optional packages that don't have USE variables. Currently I've made them all dependencies, but I was thinking of using internal USE variables, like on the mozilla ebuild. Thoughts?
Created attachment 10346 [details] Revised ebuild for GRASS 5.0.1 This ebuild covers all of the required and optional components from the REQUIREMENTS.html file that comes with GRASS, using USE variables for the optional components where possible.
Thanks guys, it's in the tree. Doug: Just as a note, careful with space-indentation, the rules say tabs :)
