On Fri, 8 Mar 2013, Bovy, Stephen wrote:
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Taylor Hedberg
Sent: Friday, March 08, 2013 8:03 AM
To: [email protected]
Subject: Re: runtime/doc/tags not ignored
Benjamin R. Haskell, Fri 2013-03-08 @ 10:43:51-0500:
runtime/doc/tags probably shouldn't be in the repository in the
first place. Neither should src/auto/configure. Both of those
things are generated from other files that are in the repo.
While it is true that configure scripts are generated from other
source files, it is customary to commit them to version control
anyway so that users can build the software without having to install
and use Autotools.
Yes
This is especially relevant for platforms like IBM z/OS where auto-tools may
not be available :)
Sure. But that can be done as some kind of "source release" step,
couldn't it? It's pretty common for there to be two kinds of source
distributions: directly from revision control (where things that are
generated aren't included, and there's some kind of "autogen.sh" script)
and "snapshot", where a version that can be "./configure && make && sudo
make install"'ed.
I guess it's not that big a deal to have them in there. It's just
annoying to have a 14,000 line file in the repo, virtually all of which
changes if you try to regenerate it with a slightly-different version of
autoconf.
So... I'll drop the issue for configure.
How about runtime/docs/tags? That one's generated by the doctags.c file
in that same dir as part of a normal build.
--
Best,
Ben
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
