From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64779 invoked by alias); 11 Jan 2019 22:16:10 -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 64771 invoked by uid 89); 11 Jan 2019 22:16:10 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=maintaining, bash, occasionally, H*c:alternative X-HELO: mail-it1-f180.google.com Received: from mail-it1-f180.google.com (HELO mail-it1-f180.google.com) (209.85.166.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 11 Jan 2019 22:16:08 +0000 Received: by mail-it1-f180.google.com with SMTP id g76so5109511itg.2 for ; Fri, 11 Jan 2019 14:16:07 -0800 (PST) MIME-Version: 1.0 References: <86acdcb9-9067-0f55-2543-6d100aaa7cae@gmail.com> <874lafey1v.fsf@Rainer.invalid> In-Reply-To: <874lafey1v.fsf@Rainer.invalid> From: "E. Madison Bray" Date: Fri, 11 Jan 2019 22:16:00 -0000 Message-ID: Subject: Re: Cygwin Statistics and curiosity To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-01/txt/msg00085.txt.bz2 On Fri, Jan 11, 2019, 21:31 Achim Gratz E. Madison Bray writes: > > I have often wondered why apt-cyg [1] hasn't been adopted fully by > > Cygwin as one of the default packages (in fact I'm not sure if there > > even is an actual cygwin package for apt-cyg), aside from the fact > > that it's not formally maintained as part of the cygwin ecosystem. > > Maybe it should be. > > For starters, apt-cyg and the handful of purported alternatives will > break your installation in subtle and not-so subtle ways. None of them > handle all postinstall actions correctly and all of them will fall over > if locked in-use files have to be altered or replaced. > I'm sure it has bugs, though it's always worked quite well for me. If I have experienced those bugs I'm not sure. I think it's possible but I'm also expert enough to usually resolve issues I've encountered on my own. At the most, I think I've had to occasionally run rebaseall after some package installs. I didn't realize its development history was such a hideous mess, especially considering that it's just a few hundred lines of bash script that I could probably rewrite myself. Personally I'd be happy to maintain it, especially if it were installed with Cygwin. Otherwise I'd just be maintaining yet another "unofficial" fork of it. Personally, I don't think a GUI program should be the only interface for installing new packages into cygwin* * modulo caveats such as using it to upgrade cygwin1.dll itself > -- 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