Note: this is in reply to a previous post, by mistake I made my reply directly to the poster rather than the list, therefore I am reposting my week-old reply now since it may be of interest to others.
14. apr. 2015 kl. 17:29 skrev wireless <[email protected]>: > On 04/14/2015 07:04 AM, Atgeirr Rasmussen wrote: >> Thank you very much, Arne Morten! >> >> I will be testing these on Ubuntu 14.04 (trusty). I would appreciate it if >> someone could test >> the 12.04 (precise) packages as well. >> >> At this point we consider 10.04 too old to support, it would have required >> significant >> extra work to pacakge for it. >> >> Atgeirr > > Ok, this is exciting news. I have not kept up with the day by day issues, so > for me to create ebuild, compile and test I need a few things > that should be pretty easy. (Not a Jenkins user, yet, but it's on my todo > list). > > 1. A list of all packages: > I looked here (http://ci.opm-project.org/job/OPM multi-PR-build/ws/) > > and found this list; is it complete and the names correct for what I should > use for gentoo? > > > dune-cornerpoint > ert > opm-autodiff > opm-benchmarks > opm-core > opm-material > opm-parser > opm-polymer > opm-porsol > opm-upscaling That should be enough, but the order is wrong, see the bottom section (Building from source) of: http://opm-project.org/download.php You could also take a look at this script: https://github.com/OPM/opm-utilities/blob/master/vagrant/clone_and_compile.sh Note that both of these assume that prerequisites are already installed. That includes ert, for which you need the latest version (that one is also marked 2015.04). > > > If so this is the master package list, these are new (to me): > ert, opm-benchmarks, opm-parser; necessitating building new ebuilds for those > packages. > > What would allow me to create ebuilds and test these packages quickly > is a direct (fully qualified) path (https:/path-to-sources.tgz) so > it is easy to grab the packages. Here is the path for the previous > version of opm-autodiff I used (from the ebuild): > > SRC_URI="https://github.com/OPM/${PN}/archive/release/${PV}/final.tar.gz -> > ${P}.tar.gz" That type of URL still works I think, but the 'final' tag has not been created yet: we are at release candidate 1, 'rc1' for all packages (except autodiff, there we are at 'rc2'). So if you want to use it now you need to replace 'final' with 'rc1' in the above URL. If you wait until the release is final, the URLs would be final as well of course. > > I can convert the fully qualified path, via http, to the ebuild > syntax, so no worries on the {parameters} defined in curly brackets. > > > What would be very cool is a list of compile time and run time > dependencies, per package, or I can grunged through the codes > for this..... > > > RDEPEND=" > >=dev-cpp/eigen-3.1:3 > dev-libs/boost > virtual/blas > virtual/lapack > sci-libs/dune-common > sci-libs/dune-istl[superlu,umfpack] > sci-libs/umfpack > >=sci-libs/superlu-4.3 > ~sci-physics/opm-core-${PV}" > > I do not think there are any new prerequisites, other than we need a little newer boost version than before. The list is also on the download page: http://opm-project.org/download.php > > > With this requested, organized information, it is trivial to retrieve > the sources, compile them, test and provide timely feedback to > the OPM team as to what I encounter. Hope this is enough to get you going, thanks for contributing! Atgeirr _______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
