Afraid I couldn't parse that debian link - no idea what any of it meant, and there was no identified problem listed there.
My concern here is that we seem to be putting something in the OMPI code base that has nothing to do with OMPI itself. Debian has had an OMPI package for awhile now, and inserting the required infrastructure to create the desired package is part of that game. I have yet to see an explanation for what changed at their level that now requires a change at ours, so perhaps that would have been the place to start.
Can someone explain what happened at the Debian packaging level? Maybe a directory is now required, or maybe some other solution would be better/appropriate.
On Nov 6, 2013, at 2:57 PM, Christopher Samuel <samuel_at_[hidden]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 07/11/13 04:40, Mike Dubman wrote:
>> I did not find debian packaging files in the OMPI tree, could you please
>> point me to it?
> As Sylvestre explained Debian (and presumably Ubuntu too) will
> automatically delete any /debian/ directory in an upstream tarball
> and substitute their own packaging.
> You can see what they put in for sid (testing) here:
> Whilst I can understand the enthusiasm I don't think it's
> going to be very helpful to Debian; perhaps a better way to
> assist would be to help out Sylvestre and the other Debian
> maintainers? This might be a handy place to start:
> All the best,
> - --
> Christopher Samuel Senior Systems Administrator
> VLSCI - Victorian Life Sciences Computation Initiative
> Email: samuel_at_[hidden] Phone: +61 (0)3 903 55545
> http://www.vlsci.org.au/ http://twitter.com/vlsci
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.14 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> -----END PGP SIGNATURE-----
> devel mailing list