I'm late replying (sigh), but I think I was the one who originally pushed for 
including autogen.pl in the tarball.  My believe is that (modulo the "right" 
autotools being installed), you should be able to rebuild the tarball from the 
tarball.  This is useful for outside organizations who want to suck in a 
"release", and add some modifications like a new BTL.  Yeah, you can pull from 
git, but every project has their own branch and tag methodologies, which can 
make for a maintenance headache.  Much easier to just suck in the tarball.

However, I do like Gilles' suggestion to make autogen.pl be a little smarter.  
If I recall correctly (and it's been a couple years now), I think that's what 
GASNet does with their bootstrap script.  Seems like everyone gets what they 
want :).

Brian

On 10/27/15, 5:23 PM, "devel on behalf of Jeff Squyres (jsquyres)" 
<devel-boun...@open-mpi.org on behalf of jsquy...@cisco.com> wrote:

>On Oct 27, 2015, at 4:46 PM, Gilles Gouaillardet <gil...@rist.or.jp> wrote:
>> 
>> my 0.02 US$ ...
>> 
>> - autogen.pl was recently used with v1.10 on a PowerPC Little Endian arch
>> (that was mandatory since the libtool we use to generate v1.10 series do not 
>> yet support PPC LE)
>
>True.  But we fixed that; it'll be in 1.10.1.
>
>> - if we remove (from the tarball) autogen.pl, should we also remove 
>> configure.ac ?
>>  and what about m4 files and Makefile.am ?
>
>Nope; if we remove those, the dependencies will be off and Bad Things will 
>happen.
>
>> - an alternative to removing autogen.pl (from the tarball) is to have 
>> autogen.pl
>>  test repo_rev and/or tarball_version from VERSION so we can detect if 
>> autogen.pl is ran
>>  from a tarball. in that case, we could fail with a message such as
>>  "you might not want to do that, but if you really do, re-run autogen.pl 
>> with the --force parameter"
>
>That's a good idea.
>
>-- 
>Jeff Squyres
>jsquy...@cisco.com
>For corporate legal information go to: 
>http://www.cisco.com/web/about/doing_business/legal/cri/
>
>_______________________________________________
>devel mailing list
>de...@open-mpi.org
>Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>Link to this post: 
>http://www.open-mpi.org/community/lists/devel/2015/10/18296.php
>



Reply via email to