bzr-builddeb has severe limitations. It is what the I used on the previous version of the PPA was built upon, and it literally only added "Autobuild changes" to the dch log.
If this some sort of branch that never got merged in, is there any way to *just* use the dch portion of it? Is there a reason why it didn't get branched in? It may be that the answer is to pull most of his code in and write a front end that doesn't do the rest of the builddeb part. I'm not sure. I would guess that this entire project would only be an hour or two with Python or bash if written from scratch. Adam Wolf Wayne and Layne, LLC On Wed, May 21, 2014 at 10:40 AM, tiger12506 <[email protected]> wrote: > > On 5/21/2014 9:37 AM, Adam Wolf wrote: > >> Hi folks, >> >> People keep asking about how to help with packaging. >> >> One of the remaining tasks for the Debian and Ubuntu PPAs for KiCad that >> needs to be done is a tool that will update the debian changelog file based >> on the bzr commit log. >> >> These tools exist for svn and git, but the bzr one just adds >> >> * Changes >> >> >> "the bzr one" -- do you have a link? I'm not familiar with the deb > making tools, so if that is a stupid question, please say so. > > Sorry if you've already found this, but is there a reason this wouldn't > work? > > https://code.launchpad.net/~evgeni/bzr-builddeb/dch > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
