From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 92010 invoked by alias); 16 Dec 2017 14:40:17 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 92001 invoked by uid 89); 16 Dec 2017 14:40:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Documents, presents, reasoned, APT X-HELO: mail-ot0-f176.google.com Received: from mail-ot0-f176.google.com (HELO mail-ot0-f176.google.com) (74.125.82.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 16 Dec 2017 14:40:15 +0000 Received: by mail-ot0-f176.google.com with SMTP id p31so3479371ota.4 for ; Sat, 16 Dec 2017 06:40:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:to:subject:references :user-agent; bh=RWfITmVwk5iDxR2CdAXmcgLPEVYGpM1SqFr0La+s80A=; b=CCZBcbbMOLurXy6jaWlRAZ23aoTMkroj+gUZhy28ExUnkuWvZvoc1CWDYLWU7kx/zi i2ULGL8tONJUmdojmdggsZC2JhE5Avyo5DlOzGbsVlos8xNMghfS8tXq2kZYD8BiyK4R EIQh1dw+4sRY0U6gv0WTrjpWhGXFCh4wyZikHSFs9uKYM6iC8u+5kPh+fj+rxa2txSN5 87U/Pitu9ZjDJf0B8pCRqr2fiXhvO7s20pu9SGr5mUXTjjQBCct33V2MICnxv9/TYVnb /aabAx5HojhEPrvru6wHRX1vJOd+YzcrmmD5ObRVc3GGLojZoo+DreBSddNux8X2bXn7 xW2g== X-Gm-Message-State: AKGB3mLYd6bsN5eN/p1Fg2xGlkV8xGqKCMsSZ/xbUS/WepYsAp7N6/kU P6ha9jK1vTLtQpTx6PB7EvrMYQ== X-Google-Smtp-Source: ACJfBos1z2xGXK4Lnw6SYKzHKtOjgoiTzsluoqF+JAA3g+2/x9A22L+dCZUiUVGYgV9NKUn+jYMj9A== X-Received: by 10.157.41.147 with SMTP id n19mr3573178otb.132.1513435213278; Sat, 16 Dec 2017 06:40:13 -0800 (PST) Received: from dwm ([2605:6000:9fc0:56:782b:4ab4:f364:a67]) by smtp.gmail.com with ESMTPSA id t27sm4000952oij.32.2017.12.16.06.40.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 16 Dec 2017 06:40:12 -0800 (PST) Message-ID: <5a35304c.9ba6ca0a.5e71f.8a99@mx.google.com> Date: Sat, 16 Dec 2017 20:47:00 -0000 From: Steven Penny X-Google-Original-From: Steven Penny To: cygwin@cygwin.com Subject: Re: setup's response to a "corrupt local copy" References: <64D09542-A92E-423B-A6C0-479A025B0759@solidrocksystems.com> Content-Type: text/plain; charset=utf8; format=flowed User-Agent: Tryst/2.0.1 (github.com/svnpenn/tryst) X-SW-Source: 2017-12/txt/msg00157.txt.bz2 On Sat, 16 Dec 2017 14:50:56, Vince Rice wrote: > No, you never need any opinion that is in conflict with yours. I'm not going > to argue with you for a variety of reasons, not least because the decision is > not yours. You have shown you don't care what anyone else thinks on this or > any other issue, and believe me, the feeling is reciprocated. I offered my > thoughts for the people whose decision this really is, and I leave it with > them. sure i do - here is example where i screwed up - and fixed a problem on my end: http://cygwin.com/ml/cygwin/2017-01/msg00236.html i do care about "the other side", when said side presents a referenced and reasoned response. you have failed to do that. you presented a use case where you were creating custom archives, then putting them in local package directory, then not updating setup.ini. wait no, that was Ken: http://cygwin.com/ml/cygwin/2017-12/msg00092.html you presented no evidence or references really: http://cygwin.com/ml/cygwin/2017-12/msg00145.html mostly and opinion post. its possible that this issue doesnt even apply to you. with ken, he is building custom archives so it applies to him. with me, i have a package manager that runs in concert with setup.exe, so it applies to me: http://github.com/svnpenn/sage do you actually have an personal experience in this matter, or did you just want to slight me and offer an opinion of someone with no experience of the issue at hand. i fear the latter. APT, DNF and ZYpp are very popular package managers, with APT being used by hundreds of thousands of people: http://stackexchange.com/leagues/76 so it makes sense that setup.exe should behave in a manner similar to APT, unless a very good reason is discovered why it shouldnt. more likely the setup.exe behavior with corrupt files was decided long ago, and without consideration to other package managers. and now that I am considering them, we maybe have some people dissenting just to dissent, with no personal experience of the issue. we are not talking removing files from: C:\Users\Vince\Documents we are talking about removing files from: C:\http%3a%2f%2fcygwin.mirror.constant.com%2f or similar, a directory specifically created by setup.exe. It is not unreasonable to expect that similar to how setup.exe has the power to remove anything from: C:\cygwin64 that it would and should have the power to remove from a directory that it created. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple