On 29 March 2017 at 13:49, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote:
> I have no objections to this.
>
> Unfortunately, I don't have the time to work on it, but we'd be glad to look
> at pull requests to introduce this functionality. :-)
Yes, yes, alright.
I am though slightly confused, following the move to GitHub.
If I go to the GiHub repo, the available release tarballs appear, for
example, as: ompi-2.0.2.tar.gz
and unpack as
drwxrwxr-x root/root 0 2017-01-31 05:54 ompi-2.0.2/
-rw-rw-r-- root/root 15724 2017-01-31 05:54 ompi-2.0.2/.gitignore
.-rw-rw-r-- root/root 4212 2017-01-31 05:54 ompi-2.0.2/.mailmap
-rw-rw-r-- root/root 3415 2017-01-31 05:54 ompi-2.0.2/.travis.yml
-rw-rw-r-- root/root 9867 2017-01-31 05:54 ompi-2.0.2/AUTHORS
..
that is, using the GitHub subproject/repo name.
However, the tarball refered to in the SRPM's SPEC-file has the
"does what it says on the tin" name:
Source: openmpi-%{version}.tar.bz2
which is also the version availble from the open-mpi.org website, and which
unpacks as
drwxrwxr-x mpiteam/mpiteam 0 2017-02-01 04:21 openmpi-2.0.2/
-rw-rw-r-- mpiteam/mpiteam 9867 2017-01-27 08:14 openmpi-2.0.2/AUTHORS
...
Are the GitHub tarballs and the "availble from the open-mpi.org
website" tarballs
the same ? (except for the git stuff)
Should they be the same, now that the development is managed at GitHub ?
What is your process behind taking the GitHub release tarball and
turning it into
the open-mpi.org one ? (or vice-versa ?)
_______________________________________________
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
