[Slackbuilds-users] bashrun2 Slackbuild typo

Robby Workman rworkman at slackbuilds.org
Fri Oct 19 18:01:20 UTC 2012

On Fri, 19 Oct 2012 22:19:42 +0700
Binh Nguyen <binhvng at gmail.com> wrote:

> On Thu, 18 Oct 2012 at 01:08 PM -0400, Chess Griffin wrote:
> > Minor typo on line 85 of the SlackBuild:
> > 
> > mv $PKG/etc/bash_completion.d/bashrun2
> > $PKGetc/bash_completion.d/bashrun2.new
> > 
> > missing a / after second $PKG so should be:
> > 
> > mv $PKG/etc/bash_completion.d/bashrun2
> > $PKG/etc/bash_completion.d/bashrun2.new
> I believe that auto-complete file like this should not be treated as a
> user-config file, i.e. it should be left as-is and not be renamed to a
> ".new" file.
> What do you maintainers think?

This is one place where I think we should probably deviate from
upstream's intentions (and I think that upstream will likely
catch up to the new bash-completion on this sooner or later).
Old bash-completion (before 2.x) put the packaged completions
files in /etc/bash-completion.d/ -- while that directory is still
supported, /usr/share/bash-completion/completions/ seems to be
intended as the systemwide/packaged completions directory whereas
/etc/bash-completion.d/ seems intended for local system overrides
and additions.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20121019/1e0ac6fe/attachment.asc>

More information about the SlackBuilds-users mailing list