From: alexmonthy@voxpopuli.im (Alexandre Montplaisir)
Subject: [lttng-dev] Building LTTNG as a debian package
Date: Thu, 21 Nov 2013 19:11:31 -0500 [thread overview]
Message-ID: <528EA133.1090500@voxpopuli.im> (raw)
In-Reply-To: <CAKvQZ_3Kus-9FnXmn_qJtVux_U+U5nPUis2es_Ws0NeMXxWqpQ@mail.gmail.com>
Hi,
The packaging for distributions is usually managed by the distribution
itself, not the upstream project.
For the official Debian packages, you can search on packages.debian.org
for the package names, and from there you can download the
*.debian.tar.gz for the packaging "recipe". Or follow the links to get
to the git tree where it is stored. For example, for the lttng-modules
package:
http://anonscm.debian.org/gitweb/?p=collab-maint/lttng-modules.git;a=summary
We also maintain a Ubuntu PPA which does automatic builds from git
roughly every day. If you want to package a git snapshot, you may find
those useful:
https://code.launchpad.net/~lttng
(under the *-packaging-daily branches)
Cheers,
Alexandre
On 13-11-21 06:24 PM, Willy Lambert wrote:
> Hi all,
>
> I have successfully build an embedded target with the LTTNG toolset and I'm
> now trying to package this to be able to repopulate a target from scratch.
>
> I'm starting with the kernel modules and I did not succeed in building them
> with make-kpkg modules_images.
>
> As I have seen you produce Debian packages for recent distributions, I
> wonder if your packaging architecture is available somewhere (I had q quick
> look on git but debian packaging infrastructure isn't present).
>
> Or maybe is there any documentation on this ?
>
> Regards.
>
next prev parent reply other threads:[~2013-11-22 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 23:24 Willy Lambert
2013-11-22 0:11 ` Alexandre Montplaisir [this message]
2013-11-22 12:28 ` Willy Lambert
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=528EA133.1090500@voxpopuli.im \
--to=alexmonthy@voxpopuli.im \
/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