[Bash-completion-devel] New completions: inline or separate files?

[Santiago M. Mola]

El dom, 11-01-2009 a las 15:16 +0200, Ville Skyttä escribió:
> Hello,

Hello Ville,

> When adding completions for new, generally available commands, is it preferred 
> to inline them in bash_completion or to add new files to contrib/?
> 
> I gather there's a more or less active plan to split bash_completion into 
> smaller files, maybe adding new completions as separate ones would make this 
> process a bit easier?
> 

In Gentoo, we split all inline completions to a separate file named
'base'. I expect upstream bash-completion to follow a similar path in
the future.

In my opinion, if 'generally available commands' are really basic
commands like the ones provided by coreutils, proc-utils, etc, I'm for
adding them inline. Otherwise, I'd prefer them in separate files.

Regards,
-- 
Santiago Moisés Mola
Jabber: cooldwind at gmail.com | GPG: AAD203B5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
 digitalmente
Url : http://lists.alioth.debian.org/pipermail/bash-completion-devel/attachments/20090111/a142608f/attachment.pgp