-
Notifications
You must be signed in to change notification settings - Fork 30
Do not keep generated autotools files under version control #40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Do not keep generated autotools files under version control #40
Conversation
|
@bryanirby, would you please review this? |
|
I need to think about this for a while. CFITSIO is a subtree of the HEASoft repository, for which it's preferable for us to have all of these files in place. So, I need time to consider options. |
|
If you keep these in the source tree, then you need to update them whenever you make changes to configure.ac or Makefile.am. They are out of date now. |
|
Duly noted, thanks. |
|
I'm not sure why this only just now started being a problem for Healpy, but since this has broken our ability to do a release it is also indirectly a release-critical issue for Debian (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100222). Please fix this ASAP. |
|
Ok, I've updated the config files on the develop branch and hope this helps. |
That worked (see healpy/healpy#998). Can you do a point release? |
c48b752 to
b90b213
Compare
|
Yes, working on 4.6.1 now. |
|
4.6.1 is published now. |
b90b213 to
83bab1c
Compare
|
I'm sorry, I spoke too soon. The healpy build is still failing with the same error as before: See https://app.readthedocs.org/projects/healpy/builds/27635307/. |
|
Ok, unfortunately I don't really know what to do here. When I re-run all of the autotools, nothing changes, so I have nothing new to commit. |
|
Does it help if you "touch aclocal.m4 configure Makefile.am Makefile.in" before the build? |
That does prevent it from regenerating and rerunning What you could do is add the macro Would you please try that? This is becoming urgent because I am getting nastygrams from fellow Debian maintainers. |
|
Ok, I just pushed changes to the develop branch to use AM_MAINTAINER_MODE. It works okay for me, let me know if it fixes things for you. |
That works. Please release that. |
|
Ok, it's released. Before future releases we'll plan to check in with you first to try to avoid any urgent scenarios. |
|
I'm not really sure where (if anywhere) this conversation is taking place, but this is a change that needs to happen. Distributing autoconf generated metafiles in git is not a good idea. That is what distribution tarballs are for. AM_MAINTAINER_MODE is not a good solution, and was abandoned decades ago. (Jim Meyering, the author of the macro, stopped using it "several years ago" as of 2006!!). If there are structural issues preventing these files from being removed from git, those are deeper issues that need to be resolved. |
|
Hi @wrp - Thanks for the note. There are structural issues underlying our historical preference for keeping the autotools-generated files in the distribution, and we weren't aware of any reasons other than aesthetic ones for removing them. However, we will revisit this issue as soon as possible. Thanks again. |
This will fix build errors that we have observed with healpy. See healpy/healpy#991 (comment).