From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout11.t-online.de (mailout11.t-online.de [194.25.134.85]) by sourceware.org (Postfix) with ESMTPS id 2F70D3858C2F for ; Sat, 2 Jul 2022 13:26:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2F70D3858C2F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=t-online.de Authentication-Results: sourceware.org; spf=none smtp.mailfrom=t-online.de Received: from fwd87.dcpf.telekom.de (fwd87.aul.t-online.de [10.223.144.113]) by mailout11.t-online.de (Postfix) with SMTP id C980C2CB5 for ; Sat, 2 Jul 2022 15:26:31 +0200 (CEST) Received: from [192.168.2.102] ([87.187.34.65]) by fwd87.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1o7d8h-2G68sy0; Sat, 2 Jul 2022 15:26:23 +0200 From: Christian Franke Subject: Re: [ITP] etckeeper 1.18.17-1 To: cygwin-apps@cygwin.com References: <36cc4e85-d20c-0f52-214d-88262f704efa@t-online.de> <20220628174122.arrqtskqzt6gzhxc@lucy.dinwoodie.org> <11b99205-0b36-a700-5a07-0ed35b3df641@t-online.de> <20220629081214.zdphk3m744nfftkv@lucy.dinwoodie.org> Message-ID: <12bbc4c0-2fa8-401e-d0df-4cfcc028c463@t-online.de> Date: Sat, 2 Jul 2022 15:26:23 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 SeaMonkey/2.53.12 MIME-Version: 1.0 In-Reply-To: <20220629081214.zdphk3m744nfftkv@lucy.dinwoodie.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-TOI-EXPURGATEID: 150726::1656768383-0142618F-54BC54AC/0/0 CLEAN NORMAL X-TOI-MSGID: cda765df-7485-4e86-bd2e-126bf2b2bc2f X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00, FREEMAIL_FROM, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2022 13:26:34 -0000 Adam Dinwoodie wrote: > On Wed, Jun 29, 2022 at 09:55:10AM +0200, Christian Franke wrote: >> Christian Franke wrote: >>> ... >> A possible simple extension which would allow the user to choose between >> manual or automatic installation+initialization: >> >> Provide an optional package, for example "etckeeper-git-init", which depends >> on etckeeper+git and only contains /etc/postinstall/etckeeper-git-init.sh >> which triggers new initialization code in >> /etc/postinstall/zp_zzz_etckeeper-postinstall.sh via some file in >> /var/cache/etckeeper. This code performs 'etckeeper init && etckeeper >> commit' if and only if VCS=git is selected and /etc/.git does not exist. > Honestly, I suspect it's not worth the effort of doing things like that. > As you say, 99.8% of users who might be interested in using etckeeper > are going to be people who already have a good idea what they're doing > and will be able to work it out for themselves. > > Thinking about it some more, I'm also mildly concerned about the small > but non-trivial proportion of users who blithely install every package > available on Cygwin, which I don't think is going to be an issue for > more-or-less any other *nix distribution. I don't normally think it's > worth doing much to actively catering for those users -- I'm generally > of the opinion that they're making their own misery -- but in this case > automatically starting etckeeper would be a potentially significant > impact, and for the sake of both their lives and yours, I suspect it's > best to just leave etckeeper as something that requires manual > initiation. Good point. > That said, if you're keen to set up that optional package, I definitely > don't think it's a bad idea; "it wouldn't be worth the effort to me" > doesn't mean you shouldn't do it!  I now decided to leave this for later (or never). The package is new and if there are still issues during initialization, the messages should be visible on console.