On Fri, Dec 30, 2011 at 12:59 PM, Rodolfo kix Garcia <k...@kix.es> wrote: > About 1: I don't know what to do. I can maintain the current code or change > to new debhelper and compat.
Your choice. I'd say maintain current code, no need to bump the version unless you really need some feature. I never used those flags because all of my packages used dh_auto_configure. Another advantage of dh_auto_configure is that if policy changes (or default configure build flags), dh_auto_configure will take care of it for you. You can look into if dh_auto_configure will work for you, I don't know too much about the options you're passing it, but maybe it will. > About 3: Jakub sent a comment about it. What should I do? I think Jakub and I agree that if you're using simple dh rules, you probably can use --with autotools-dev to take care of the config.sub/config.guess files properly. > About 4: Yes, debian folder has a lot of files. I moved some of them to one > directory in the last upload. I leave it here because I sent a patch to the > wmaker-crm upstream (http://lists.windowmaker.org/dev/msg02488.html), but is > not applied yet. The comment was more about the override_dh_clean target. I was just pointing out an alternative to overriding the dh_clean target is to use a debian/clean file (see the manpage of dh_clean). You can chose either way of doing it, up to you. > About 5: Perfect. I will update the next version > About 6: The debian folder is included in the upstream, because is used to > make the nigthly packages. I am not sending the changes to the upstream yet > to avoid disturb the mail list. I am waiting to upload the package to > debian, and then send only one patch to the upstream. It's ok to have a separate VCS just for debian packaging [1]. Upstream's VCS is for their development, you can have your own VCS which is for packaging. Even if upstream is using a VCS, it is encouraged to keep your packaging in a VCS as well. For example, https://github.com/LibreCAD/LibreCAD http://anonscm.debian.org/gitweb/?p=debian-science/packages/librecad.git It is very possible that your debian/ will be different than upstream debian/ because you two have different goals: your packaging for distribution in Debian main and they are packaging for nightly builds. Also, it is possible that someone, besides you, will do an NMU at some point. ~Scott -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cang8-ddjwktblw1jret0kdsxfe6btzfz4-szk3odisxm2j2...@mail.gmail.com
