{"thread":{"id":"2403","subject":"Regarding: Debian: packaging updates.","startedAt":"2005-11-08T17:08:26Z","lastAt":"2005-11-09T23:06:38Z","messageCount":5,"participants":["Johannes Schindelin","Simon Richter","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"11331","messageId":"Pine.LNX.4.63.0511081806320.18374@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"2403","inReplyTo":null,"subject":"Regarding: Debian: packaging updates.","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2005-11-08T17:08:26Z","receivedAt":"2005-11-08T17:08:26Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nI notice that there are files like \"git-core.files\". Wouldn't it be better \nto generate them from the Makefile? The same mechanism could then be used \nto make RPMs from the same Makefile.\n\nCiao,\nDscho\n"},{"id":"11338","messageId":"4370EEF7.4060708@debian.org","threadId":"2403","inReplyTo":"Pine.LNX.4.63.0511081806320.18374@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: Regarding: Debian: packaging updates.","fromName":"Simon Richter","fromEmail":"sjr@debian.org","sentAt":"2005-11-08T18:31:19Z","receivedAt":"2005-11-08T18:31:19Z","isPatch":false,"sender":{"key":"sjr@debian.org","avatar":null},"body":"Hi,\n\nJohannes Schindelin wrote:\n\n> I notice that there are files like \"git-core.files\". Wouldn't it be better \n> to generate them from the Makefile? The same mechanism could then be used \n> to make RPMs from the same Makefile.\n\nI'm currently in the process of working my way through the current \npackaging, and there is quite a lot I am going to simplify. As the \nDebian build scripts do not expect this file to be autogenerated, I \nthink it would be counterproductive to do so; it can seriously affect \nreproducability of builds.\n\n(actually, I would like to ask not to fix things in the Debian packaging \nthat aren't broken, as providing an upgrade path for earlier versions \nwill be a lot less painful then)\n\n Simon\n"},{"id":"11339","messageId":"7vbr0vey42.fsf@assigned-by-dhcp.cox.net","threadId":"2403","inReplyTo":"4370EEF7.4060708@debian.org","subject":"Re: Regarding: Debian: packaging updates.","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-11-08T19:30:21Z","receivedAt":"2005-11-08T19:30:21Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Simon Richter writes:\n\n> I'm currently in the process of working my way through the current \n> packaging, and there is quite a lot I am going to simplify. As the \n> Debian build scripts do not expect this file to be autogenerated, I \n> think it would be counterproductive to do so; it can seriously affect \n> reproducability of builds.\n>\n> (actually, I would like to ask not to fix things in the Debian packaging \n> that aren't broken, as providing an upgrade path for earlier versions \n> will be a lot less painful then)\n\nNoted. I just barely speak enough deb to build binary packages,\nand the source packaging and upload procedure are something I've\nnever bothered to learn, so I won't be touching that area from\nnow on.\n\nSince you have debian.org e-mail address, perhaps you can feed\nme patches to debian/ area and deb: rule in the main Makefile?\nI was asked to use dpkg-buildpackage/dpkg-genchanges and produce\nthe *.changes file as well by somebody who maintains his own\nprivate apt source. I'd appreciate if you can take care of it\nwhen you update the Makefile deb: rule as well, if the *.changes\nfile request makes sense to you.\n"},{"id":"11343","messageId":"4370FE57.7010304@debian.org","threadId":"2403","inReplyTo":"7vbr0vey42.fsf@assigned-by-dhcp.cox.net","subject":"Re: Regarding: Debian: packaging updates.","fromName":"Simon Richter","fromEmail":"sjr@debian.org","sentAt":"2005-11-08T19:36:55Z","receivedAt":"2005-11-08T19:36:55Z","isPatch":false,"sender":{"key":"sjr@debian.org","avatar":null},"body":"Hi,\n\nJunio C Hamano wrote:\n\n> Since you have debian.org e-mail address, perhaps you can feed\n> me patches to debian/ area and deb: rule in the main Makefile?\n\nSure. I have also talked this over with a few people and am going to \nmake official uploads occasionally.\n\n> I'd appreciate if you can take care of it\n> when you update the Makefile deb: rule as well, if the *.changes\n> file request makes sense to you.\n\nNot really. *.changes files make only sense if you are running archive \nmaintenance software, and the need to do that should go away with \nreasonably up-to-date packages being in the archive RSN.\n\n Simon\n"},{"id":"11424","messageId":"7v7jbha0ap.fsf@assigned-by-dhcp.cox.net","threadId":"2403","inReplyTo":"4370FE57.7010304@debian.org","subject":"Re: Regarding: Debian: packaging updates.","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-11-09T23:06:38Z","receivedAt":"2005-11-09T23:06:38Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Simon Richter writes:\n\n> Junio C Hamano wrote:\n>\n>> Since you have debian.org e-mail address, perhaps you can feed\n>> me patches to debian/ area and deb: rule in the main Makefile?\n>\n> Sure. I have also talked this over with a few people and am going to \n> make official uploads occasionally.\n\nSimon, I've received a patch to do *.changes file from Carl\nBaldwin, and with his permission I am forwarding it to you,\nhoping that you could include it (or reject it with explanation\nto Carl and me) when you feed me your debian/ updates. Carl\nsays he wants to use dupload to populate his private apt-get\nrepository and the process wants the generated *.changes file.\n\nMyself, I've been either installing with \"dpkg -i\" directly or\npopulating the apt-get repository by hand (yuck) but if dupload\nis the preferred way to maintain private apt-get repository and\nif having *.changes file helps that procedure, then...\n\n\n---\ndiff --git a/Makefile b/Makefile\nindex bfdaf76..c1fcecb 100644\n--- a/Makefile\n+++ b/Makefile\n@@ -452,8 +452,7 @@ rpm: dist\n deb: dist\n rm -rf $(GIT_TARNAME)\n $(TAR) zxf $(GIT_TARNAME).tar.gz\n- dpkg-source -b $(GIT_TARNAME)\n- cd $(GIT_TARNAME) && fakeroot debian/rules binary\n+ cd $(GIT_TARNAME) && dpkg-buildpackage -rfakeroot -us -uc\n\n ### Cleaning rules\n\n@@ -464,6 +463,7 @@ clean:\n rm -rf $(GIT_TARNAME)\n rm -f $(GIT_TARNAME).tar.gz git-core_$(GIT_VERSION)-*.tar.gz\n rm -f git-core_$(GIT_VERSION)-*.dsc\n+ rm -f git-core_$(GIT_VERSION)-*.changes\n rm -f git-*_$(GIT_VERSION)-*.deb\n $(MAKE) -C Documentation/ clean\n $(MAKE) -C templates clean\n"}]}