On Mon, 30 Sep 2019 at 09:23, Mark Thomas <ma...@apache.org> wrote: > > On 29/09/2019 23:15, Gary Gregory wrote: > > On Sun, Sep 29, 2019 at 6:04 PM sebb <seb...@gmail.com> wrote: > > > >> On Sun, 29 Sep 2019 at 22:36, Matt Sicker <boa...@gmail.com> wrote: > >>> > >>> I’m sort of going off of what GNU projects do (they use autotools for > >> any C > >>> projects), but the common ‘./configure && make && sudo make install’ > >>> snippet is almost timeless. > >> > >> Not sure what that has to do with the question at hand, i.e > >> > >> Is the file is allowed to be in the source artifact if it is not in > >> the source repository? > >> > > > > For me, no, I expect the source zip/tar to be a subset of what is in the > > repo for the purposes of building usable artifacts, not a super-set. > > That goes against the standard practice which is not to put the > configure script under version control.
It's perfectly OK not to put generated files under version control. I don't think it's OK to include files in the source archive that are not in the tag. > I assume that this is because the file is generated. If it is created as part of the build, why is it included in the source archive? > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
