RESOLVED FIXED 116229
[jhbuild] Should remove the sources directory as well when cleaning
https://bugs.webkit.org/show_bug.cgi?id=116229
Summary [jhbuild] Should remove the sources directory as well when cleaning
Gustavo Noronha (kov)
Reported 2013-05-16 08:56:53 PDT
[jhbuild] Should remove the sources directory as well when cleaning
Attachments
Patch (1.53 KB, patch)
2013-05-16 08:57 PDT, Gustavo Noronha (kov)
no flags
Gustavo Noronha (kov)
Comment 1 2013-05-16 08:57:35 PDT
Gustavo Noronha (kov)
Comment 2 2013-05-16 08:59:27 PDT
This build failure resulted from jhbuild not noticing the patches applied to a source tree have changed: https://webkit-queues.appspot.com/results/484327 Although this is arguably a bug in jhbuild, we have suffered problems with builds failing because the clean was not clean enough before, and I couldn't think of a reason why we should not want a full clean rebuild (including checkout and patching) when changing the jhbuild configuration, so this is my proposal.
Martin Robinson
Comment 3 2013-05-16 10:29:43 PDT
Hrm. Isn't it a bit of pain to redownload everything?
Gustavo Noronha (kov)
Comment 4 2013-05-16 10:57:56 PDT
It is indeed, but I think we change the jhbuild modules seldom enough that the reduced complexity pays off.
Martin Robinson
Comment 5 2013-05-16 11:02:12 PDT
Comment on attachment 201962 [details] Patch Okay. We can give it a shot and then rework it if there are mobs outside our houses. :)
Gustavo Noronha (kov)
Comment 6 2013-05-16 12:09:32 PDT
Comment on attachment 201962 [details] Patch Clearing flags on attachment: 201962 Committed r150198: <http://trac.webkit.org/changeset/150198>
Gustavo Noronha (kov)
Comment 7 2013-05-16 12:09:38 PDT
All reviewed patches have been landed. Closing bug.
Philippe Normand
Comment 8 2013-05-31 02:28:07 PDT
This is a radical change... Can't we instead make jhbuild smarter? Removing gigabytes of Source/ without even a confirmation prompt was a bad surprise for me this morning...
Note You need to log in before you can comment on or make changes to this bug.