From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111934 invoked by alias); 25 Feb 2016 10:05:13 -0000 Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com Received: (qmail 111758 invoked by uid 89); 25 Feb 2016 10:05:12 -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,SPF_PASS autolearn=ham version=3.3.2 spammy=pant, easiest, rolling, seeking X-HELO: mail-wm0-f52.google.com Received: from mail-wm0-f52.google.com (HELO mail-wm0-f52.google.com) (74.125.82.52) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 25 Feb 2016 10:05:10 +0000 Received: by mail-wm0-f52.google.com with SMTP id g62so20764753wme.1 for ; Thu, 25 Feb 2016 02:05:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=RfHtr7HaxV1lwldeVRqEooH+JX71MEILj+BOWA3Eeek=; b=Nv+lN8qj6NgTym5d887Q7IpsZGK2ju9PT5g3Nj85FqRaAG1JtSWzLuKoCiEJdHGmpO dCReXjwJ7IA4+jjYkz63CColNeIiCyrK8jJsZszzhimWIG6zV/IhYatDaFznNIs9Z0KW MhntATz9uyNEYTxv9TXxwq++u9RK2NTUyQeWawhHnPYhjZyP8Scfzr65+3xqnzwipN1Q m9sON/sD4ijfOiAL1PskoGW8i/ka3cZD9PxP/LKcxjOL/XxMX2pE+CfsmKS8Fv40WJOV RI2Uv3sJxEt/SdsXalrd6ScVHZzuaYx6nb++onrNXTZYle2XZ7/Bu/hQSxQdMqpxLKc4 p24w== X-Gm-Message-State: AG10YOR3U7UJ3/e/bnulBm1Uh0iqex3OcdABeyI6dGFRXQAQsQ1DFR46Nip6/F3ntxT5Wg== X-Received: by 10.28.158.8 with SMTP id h8mr2729129wme.6.1456394707149; Thu, 25 Feb 2016 02:05:07 -0800 (PST) Received: from dinwoodie.org ([2001:ba8:0:1c0::9:1]) by smtp.gmail.com with ESMTPSA id z127sm2437511wme.5.2016.02.25.02.05.06 for (version=TLS1_2 cipher=AES128-SHA bits=128/128); Thu, 25 Feb 2016 02:05:06 -0800 (PST) Date: Thu, 25 Feb 2016 10:05:00 -0000 From: Adam Dinwoodie To: cygwin-apps@cygwin.com Subject: Separate packages for completion scripts? Message-ID: <20160225100504.GD29016@dinwoodie.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes X-SW-Source: 2016-02/txt/msg00081.txt.bz2 Seeking opinions from other package maintainers: is it desirable to have Bash (et al.) completion scripts as part of the main package they're associated with, or should they be packaged separately? Currently, the two packages I maintain (fzf and Git) both have separate packages for their Bash completion scripts. For Git, that was the behaviour when I adopted the package, and for fzf I copied the example set by Git. Looking now, the only other package that has its Bash completion script as a separate install to the main package is dbus; everything else just includes the completion scripts as pant of the main package.[0] I'm thinking about this in the context of packaging Ag, which also has a Bash completion script, and I'm thinking including it in the main package is the easiest option, both from my perspective and from an end-user perspective. The only disadvantages I can think of are for people who definitely don't want the completion script even though they do want the tool and they do want the rest of bash-completion, but I could well believe that's an empty set. Does anyone here have any preferences or opinions? I'm currently thinking I'll package Ag's completion script in the main package, and look at rolling the other completion scripts into the main package when I get around to switching to use pkg-config to get the relevant directory names. [0]: https://cygwin.com/cgi-bin2/package-grep.cgi?grep=etc%2Fbash_completion.d%5C%7Cusr%2Fshare%2Fbash-completion%2Fcompletions&arch=x86_64