From: Michael Lippautz <michael.lippautz@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe 0/6] add syslog-ng/eventlog/libnet
Date: Wed, 20 Apr 2011 09:18:08 +0200 [thread overview]
Message-ID: <cover.1303283391.git.michael.lippautz@gmail.com> (raw)
This is an re-import and upgrade from org.oe.dev. If everything is fine I can
also apply them to org.oe.dev.
libnet:
* libnet at packetfactory.net is dead...
* Get the latest version from a github fork that claimes to update and maintain
it
* README tells it's compatible with libnet-1.1
* dynamic build, instead of static
* removed cruft that is handled by autotools class
* removed already applied patches and rebased endianess one
eventlog: minor upgrade
syslog-ng:
* adapt EXTRA_OECONF
* move to latest stable (3.2.2)
Pull URL: git://gitorious.org/oe-zoid/meta-openembedded.git
Branch: master
Browse: http://gitorious.org/oe-zoid/meta-openembedded/commits/master
Thanks,
Michael Lippautz <michael.lippautz@gmail.com>
---
Michael Lippautz (6):
syslog-ng: Re-import 2.0.5 from org.oe.dev
eventlog: Re-import 0.2.5 from org.oe.dev
eventlog: Clean recipe and upgrade to 0.2.12
libnet: Re-import 1.1.2.1 from org.oe.dev
libnet: Clean and upgrade (see below)
syslog-ng: Update to 3.2.2
.../libnet/libnet-1.1.5/fix-endianess-test.patch | 38 +++
.../recipes-connectivity/libnet/libnet_1.1.5.bb | 24 ++
.../recipes-support/eventlog/eventlog_0.2.12.bb | 11 +
meta-oe/recipes-support/syslog-ng/files/initscript | 45 +++
.../recipes-support/syslog-ng/files/syslog-ng.conf | 338 ++++++++++++++++++++
meta-oe/recipes-support/syslog-ng/syslog-ng.inc | 78 +++++
.../recipes-support/syslog-ng/syslog-ng_3.2.2.bb | 10 +
7 files changed, 544 insertions(+), 0 deletions(-)
create mode 100644 meta-oe/recipes-connectivity/libnet/libnet-1.1.5/fix-endianess-test.patch
create mode 100644 meta-oe/recipes-connectivity/libnet/libnet_1.1.5.bb
create mode 100644 meta-oe/recipes-support/eventlog/eventlog_0.2.12.bb
create mode 100644 meta-oe/recipes-support/syslog-ng/files/initscript
create mode 100644 meta-oe/recipes-support/syslog-ng/files/syslog-ng.conf
create mode 100644 meta-oe/recipes-support/syslog-ng/syslog-ng.inc
create mode 100644 meta-oe/recipes-support/syslog-ng/syslog-ng_3.2.2.bb
--
1.7.3.4
next reply other threads:[~2011-04-20 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 7:18 Michael Lippautz [this message]
2011-04-20 7:18 ` [meta-oe 1/6] syslog-ng: Re-import 2.0.5 from org.oe.dev Michael Lippautz
2011-04-20 7:18 ` [meta-oe 2/6] eventlog: Re-import 0.2.5 " Michael Lippautz
2011-04-20 7:18 ` [meta-oe 3/6] eventlog: Clean recipe and upgrade to 0.2.12 Michael Lippautz
2011-04-20 7:24 ` Martin Jansa
2011-04-20 7:18 ` [meta-oe 4/6] libnet: Re-import 1.1.2.1 from org.oe.dev Michael Lippautz
2011-04-20 7:18 ` [meta-oe 5/6] libnet: Clean and upgrade (see below) Michael Lippautz
2011-04-20 7:30 ` Martin Jansa
2011-04-20 7:19 ` [meta-oe 6/6] syslog-ng: Update to 3.2.2 Michael Lippautz
2011-04-20 8:31 ` [meta-oe 0/6] add syslog-ng/eventlog/libnet Koen Kooi
2011-04-20 9:26 ` state of oe and meta-oe (was: 0/6] add syslog-ng/eventlog/libnet) Paul Menzel
2011-04-20 10:00 ` state of oe and meta-oe Koen Kooi
2011-04-20 10:08 ` Paul Menzel
2011-04-20 14:03 ` [meta-oe 0/6] add syslog-ng/eventlog/libnet Michael Smith
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=cover.1303283391.git.michael.lippautz@gmail.com \
--to=michael.lippautz@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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