[lttng-dev] Bash completion v0.00001

[David Goulet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12-01-24 10:28 AM, Alexandre Montplaisir wrote:
> On 12-01-24 09:59 AM, David Goulet wrote:
>>
>>
>> On 12-01-24 09:47 AM, Mathieu Desnoyers wrote:
>>> * Simon Marchi (simon.marchi at polymtl.ca) wrote:
>>>> Hi,
>>>>
>>>> This is my first or so version of the programmable bash completion
>>>> (tab completion) for the LTTng 2.0 command line tool:
>>>>
>>>>
>> http://git.dorsal.polymtl.ca/~smarchi?p=lttng-bash-completion.git;a=blob;f=lttng;hb=HEAD
>>>>
>>>> Currently, it is able to complete general options (before the
>>>> command), the command names and command-specific options (after the
>>>> command). The patch I sent earlier today for lttng-tools is needed for
>>>> the completion to work, so if you want to try it, you can either wait
>>>> for it to be merged or apply it yourself.
>>>>
>>>> Install instructions for Debian-based distros:
>>>>
>>>> 1- Make sure that the bash-completion package is installed on your
>> system
>>>> 2- Copy the file in /etc/bash_completion.d
>>>> 3- Type source /etc/bash_completion
>>>>
>>>> In the future, it would be interesting to be able to complete session
>>>> names, channel names, and maybe perf counter names, which look like a
>>>> big headache to type by hand.
>>
>>> It would be nice to figure out where we could package it in the
>>> lttng-tools. Maybe in a extras/ directory ? Thoughts ?
>>
>> Yes normally, you can find these kind of things in contrib/ or extras/.
>>
>> We can thing also of default init script, basic setup script, and so on...
>>
>> David
> 
> 
> Or just leave it at the top level, it's only one file after all. In any
> case, we should put that kind of thing at the same place as the
> pkg-config (.pc) files.

Well, it could, however, this is one file of potentially *many* that we can make
available. I can think of init script, default configuration (when lttng.conf
will come), third part software for lttng-tools, and so on.

I think extras/ might be the way to go with that.

For you Alex (packaging), does this creates problem?

Cheers!
David

> 
> 
> Alex
> 
>>
>>
>>> Thanks,
>>
>>> Mathieu
>>
>>>>
>>>> Comments are welcome.
>>>>
>>>> Thanks,
>>>>
>>>> Simon
>>>>
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJPHtBJAAoJEELoaioR9I02i1kH/A2p9UfxwKANJ0oh5q2bc7ye
d2+7f6krIJG34Y+E6rfcnNIAJSVwbDLc/7oaqs1VB926198XoS0mVFsijUhTY73H
AfP4UKAKQ35/C0oFsRti3D5j0s0LDDXp08HiUqQhV2Ankqhvf0zlToSyYfjjAdo9
xwr6QJDLL53k6I7CKrdvqK0/Lrf55+Q745kGvH0+AEq8LLaytVdf57Xw3tDe/HTO
3tUcOfQ00yi4wOBIYYgHX8g7BiWZjvnFCC/NHmRwHNE1peulOujCfsoMrFGGluag
q3AlrtADVJlGtMF8G1uU0ZRaOmdpeyMpFN0b0IvZrrjIbFTbHSoxTzxUHp8Apvc=
=CZXy
-----END PGP SIGNATURE-----