Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Peter Wienemann Newsgroups: linux.debian.maint.python Subject: Re: Upload request: psrecord (NEW) Date: Sun, 08 Dec 2024 18:40:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Dec 8 17:36:49 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-109.849 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.34, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Debian-User: wiene X-Mailing-List: archive/latest/22652 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/0f87d667-6649-4a9b-8cc6-92c1724e8bf2@debian.org Approved: robomod@news.nic.it Lines: 18 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Sun, 8 Dec 2024 18:36:32 +0100 X-Original-Message-ID: <0f87d667-6649-4a9b-8cc6-92c1724e8bf2@debian.org> X-Original-References: <80fe104d-453c-4555-b656-c3123a3bbe35@debian.org> <2f0bf5b0ed4df279b81295343eacf66f9d5ddf35.camel@gmail.com> <3145534b-cf5e-4cd9-b0f6-23133f24914a@debian.org> <606c0e77e2ef7a267919957015dccc7d2bb51e7f.camel@gmail.com> <735d8e62-33ed-47c1-a64a-c5a7800f09fc@debian.org> <78dd4de9-1eea-4e3a-a284-0d7ae64f0e0f@web.de> Xref: csiph.com linux.debian.maint.python:16562 Hi Ananthu, On 2024-12-08 17:58:09, weepingclown wrote: > d/clean would work just as well, that's exactly what I tend to use if I have more than a few files that I have to specify manually to be cleaned. I always feel undecided which option I should give preference to. > And personally, I'd recommend to use execute_after_dh_auto_clean than override_dh_auto_clean so that it doesn't override anything it was previously doing, just in case. As long as the override_dh_auto_clean target still contains dh_auto_clean the original functionality should be retained. At least this is my understanding. Please correct me if this is wrong. But you are perfectly right that using execute_after_dh_auto_clean is less error-prone. Thanks for this suggestion. I added it to my notes. :-) Best regards Peter