Conversation
|
@DBezemer not sure if you saw this, so ping! |
|
@thedoc31 thanks for the changes, I'm considering that we could empty out the whole SOURCES dir instead as multiple other archives could be placed there as well when building with some options, any comment/concern to that? |
None at all, I was conservative in case there was something else I hadn't thought of. I'll update the PR. |
Using DBezemer's suggestion to remove entire SOURCES folder to be extra sure it's starting fresh
|
@DBezemer Done! Have a look. |
|
@thedoc31 I just realized clearing out SOURCES will also remove the files provided by the repo, so I think removing all .tar.gz files only is a better idea so it clears up both the LUA archive and the HAP archive. Apologies for the roundabout on this :) |
No problem, thanks! |
Yesterday, I built haproxy 2.8.5 using
make MAINVERSION=2.8, which downloadedhaproxy-2.8.5.tar.gzinto./SOURCES. Today, 2.8.6 was released so I wanted to build it, but start fresh. I issuedmake clean, but the code tried to removehaproxy-2.4.25.tar.gzwhich was obviously incorrect, and thehaproxy-2.8.5.tar.gzfile remained.make clean MAINVERSION=2.8did not work either, because it wants to removehaproxy-2.8.6.tar.gz(the current upstream version) and nothing else.The way
make cleanis configured now, it will only try to remove whatever the current upstream version ofMAINVERSIONis rather than removing any/all versions which might happen to be in./SOURCES. This could also get messy for people who might be using the same build box for multipleMAINVERSIONversions, say2.7and2.8.Therefore, for
make cleanto work as I would expect it to, I propose we remove all./SOURCES/haproxy-*.tar.gzarchives.Lastly, the git diff is showing I removed the last line feed from EOF but I didn't - it's still there in code. I am not sure why git is reporting it as a change; I tried to put the line feed back, but just got an empty commit
a364d0f. 🙄 Apologies for the mess.