Created attachment 384680 [details]
Here is some ebuilds for meteorology.
Including following packages verified to work:
sci-libs/g2clib : library for reading/writing GRIB2 files, used by wgrib2, GrADS
sci-libs/gadap : library for reading/writing OPeNDAP station data, used by GrADS
sci-libs/gctpc : library for geolocation routines, used by wgrib2
sci-libs/esmf : library for building numerical meteorology models, used by NCL (not included)
sci-geosciences/wgrib : application that reads/writes/modifies a GRIB(1) file
sci-geosciences/wgrib2 : application that reads/writes/modifies a GRIB2 file
aux_progs are not built, ipolates is not built because of license issue of FFT code.
sci-geosciences/grib2ctl : script that creates ctl files for GrADS, not included in GrADS, but necessary to handle GRIB files in GrADS
sci-geosciences/g2ctl : same as above but works on a GRIB2 file
x11-libs/libsx : this is a library required to build GrADS
sci-geosciences/grads : an interactive desktop tool that is used for easy access, manipulation, and visualization of earth science data.
This is my first ebuild commit, please tell my where I can improve.
I'd suggest you publish your ebuilds via an overlay (probably github.com would be a good place), and see if you can attract any user/dev.
btw, "open one bug per ebuild" would be good scheme, you can use this bug for tracker (eg. bug #471102) if you like..
I'm not familiar with overlays, are there any suitable overlays for geo-science / meteorology?
I will try to contact some users.
Comment on attachment 384680 [details]
What is needed is a separate bug report per package (i.e. [category/package]). Dumping everything in a single bug report is a sure way to a very long lifetime of the bug report with many comments and lots of side-tracking. Filing separate bug reports ensure that some of the ebuilds get included in the tree more easily and earlier.
Please file separate bug reports for each package.