(22:01:19) blahdeblah: Q for cvs-buildpackage users: what is the correct/recommended way to build a native package (i.e. where the upstream version source is in the same CVS tree)?
(22:05:11) blahdeblah: I've experimented with debian/ being tagged with debian_version_X_Y_Z-A and the remaining source being tagged as upstream_version_X_Y_Z. This results in a non-buildable package when exported by cvs-buildpackage, whereas if i just cvs export all the files, it works fine. Do i need to set up rules more like an upstream package than a native package?
(22:08:43) blahdeblah: Is everyone scared away by the mention of cvs-buildpackage, or am i just too verbose?
IRC logs
Edited logs of IRC discussions that might be helpful when keyword searching.
Debian revision control systems IRC discussion
Debian development quasi-reference
(17:47:01) blahdeblah: Hi, i'm looking for some best practices suggestions. Can anyone point me to documentation/tools relating to:
(17:47:01) blahdeblah: 1. maintaining packages in CVS and generating .debs from them
(17:47:01) blahdeblah: 2. maintaining apt repositories with the results from 1
(17:47:01) blahdeblah: I've found apt-ftparchive in the apt-utils package - is this the recommended tool for 2?
(17:47:19) Overfiend: blahdeblah: apt-get install cvs-buildpackage
(18:20:05) blahdeblah: Overfiend: thanks for that cvs-buildpackage suggestion - looks good. Is apt-ftparchive the right thing to be looking at for apt repository maintenance?
