Easy answer: just let debhelper do the work for you. Makes packaging quite a bit easier and takes care of a good deal of policy grunt work like the usr/doc -> usr/share/doc symlinking. it looks like dpkg --build should do the right thing, my two packages that do not use debhelper do not call dpkg-genchanges. One is multi-binary the other is a task package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
- [Q] dpkg-buildpackage not generating .changes file.... Sudhakar Chandra
- RE: [Q] dpkg-buildpackage not generating .chan... Sean 'Shaleh' Perry
- Re: [Q] dpkg-buildpackage not generating .chan... Sudhakar Chandra
- Re: [Q] dpkg-buildpackage not generating .chan... Sean 'Shaleh' Perry
- Re: [Q] dpkg-buildpackage not generating .chan... Antti-Juhani Kaijanaho
- Re: [Q] dpkg-buildpackage not generating .chan... Sudhakar Chandra
- Re: [Q] dpkg-buildpackage not generating .chan... Antti-Juhani Kaijanaho