Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: david.goulet@polymtl.ca (David Goulet)
Subject: [ltt-dev] UST communication library
Date: Wed, 15 Jun 2011 11:24:10 -0400	[thread overview]
Message-ID: <4DF8CE9A.9060700@polymtl.ca> (raw)
In-Reply-To: <4DF8CE12.1080309@gmail.com>

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

Exactly! Thus having a hard dependency is completely out of question.

On 11-06-15 11:21 AM, Yannick Brosseau wrote:
> 
>> Enlighten me Yannick :)
>>
>> # apt-get install lttng-tools
>>
>> How are you going to have the UST support without installing the UST
>> package
>> (assuming that libustcomm is inside ust) ?
>>
>> I figure you'll have a "Not found libust.so..." at execution time ?
> 
> Exactly, for the *runtime* dependency, that would be a *recommand* and
> we detect if libusb is present or not. But  that's really up to the
> packager to decide how he does it. Each distro might have their own
> policies.
> 
> As the upstream developer, you should let the user decide if he want UST
> support or not. I might be building an embedded system were space is a
> constraint and I would want to only  have the kernel tracer and not
> bother with he userspace one.
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJN+M6aAAoJEELoaioR9I02y2AIALFkB/eEGG6V5of2dDPZ3NbL
MegoK0zV1rOh4XlMTuncdIfez7m21eore9FwkLvc2Lc6C0YpmbTmYnJgT52Ngz86
5L5YsHdpnYbkJ929UHwRZNByITmWRMJo71kI8+FAra5zw5EsVA5uRPJs6rvvsqlL
Xly+ldJsSUBE2B+1/dlx3oGugQ/3UqszPGdkFIml6HXZo1MnzlYljHg4r1x7a/eq
gjFGhlrqRuEC0orYrErK/F647Ng7WZmUcVGHp/5bThXWfKjUjymgNJFzz03YRixl
/us0FsZJr7n7Fz34AgJP7qEp/qcgcyGchcaI0seCYmr4yTbgnw1BvGuxzW6BTLg=
=zqFf
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-06-15 15:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 21:26 David Goulet
2011-06-15  5:23 ` Alexandre Montplaisir
2011-06-15  8:09   ` Nils Carlson
2011-06-15 14:57   ` David Goulet
2011-06-15 15:01     ` Yannick Brosseau
2011-06-15 15:16       ` David Goulet
2011-06-15 15:21         ` Yannick Brosseau
2011-06-15 15:24           ` David Goulet [this message]
2011-06-15 15:26             ` Yannick Brosseau
2011-06-15 15:41               ` Mathieu Desnoyers
2011-06-15 18:51         ` Alexandre Montplaisir
2011-06-15 15:06 ` Yannick Brosseau
2011-06-15 15:13   ` David Goulet
2011-06-15 15:16     ` Yannick Brosseau
2011-06-15 15:32     ` Mathieu Desnoyers
     [not found]     ` <BLU0-SMTP5372DAF7E219ACFC9DE44C966B0@phx.gbl>
2011-06-15 15:55       ` Yannick Brosseau
2011-06-15 17:16         ` Mathieu Desnoyers
2011-06-15 19:11           ` Alexandre Montplaisir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DF8CE9A.9060700@polymtl.ca \
    --to=david.goulet@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox