From: David Woodhouse <dwmw2@infradead.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Daryl Van Vorst <daryl@wideray.com>,
"'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Alignment issue
Date: Thu, 12 Aug 2004 11:35:36 +0100 [thread overview]
Message-ID: <1092306935.15466.74.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <1092306154.28711.85.camel@pegasus>
On Thu, 2004-08-12 at 12:22 +0200, Marcel Holtmann wrote:
> btw what is the status of BlueZ for Fedora Core. Currently I know the
> status of them for Debian and SuSE. Are there any extra patches that I
> must know of?
We have a patch to make various daemons build PIE and we mangle the
defaults in some config files -- other than that nothing interesting. I
went through it all quite recently and made sure you had the one or two
other patches that made sense.
> How do you split the bluez-utils into different packages?
We have these packages:
bluez-bluefw-1.0-5.ppc.rpm
bluez-hcidump-1.10-1.ppc.rpm
bluez-libs-2.9-1.ppc.rpm
bluez-libs-devel-2.9-1.ppc.rpm
bluez-pin-0.23-2.ppc.rpm
bluez-utils-2.9-1.ppc.rpm
bluez-utils-cups-2.9-1.ppc.rpm
We do split the bluez-utils init scripts up, as discussed a few weeks
ago. I have patches outstanding for initscripts which make 'ifup bnep0'
responsible for starting pand, to make it just like a normal interface
-- even pppd is started that way, not by an initscript.
> > Autocrap considered harmful; I'd rather let the compiler do it.
>
> Actually I meant to let autoconf compile some test code, then run it and
> analyse that result.
/me shudders. Autocrap considered harmful. You break cross-compilation
if you try to do that. I'd much prefer just to write portable code.
> For now I will use memmove, but we need clarification on this. I lost my
> Sun Ultra system, so I can't do any tests.
We keep our compiler-dudes in the US mostly so they're sleeping. I'll
poke one when they wake up.
--
dwmw2
next prev parent reply other threads:[~2004-08-12 10:35 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 18:38 [Bluez-devel] Alignment issue Daryl Van Vorst
2004-08-10 23:12 ` Marcel Holtmann
2004-08-11 9:20 ` Stephen Crane
2004-08-11 11:08 ` David Woodhouse
2004-08-11 19:33 ` Marcel Holtmann
2004-08-11 7:13 ` Marcel Holtmann
2004-08-11 16:44 ` Daryl Van Vorst
2004-08-11 19:31 ` Marcel Holtmann
2004-08-12 8:34 ` David Woodhouse
2004-08-12 9:27 ` Marcel Holtmann
2004-08-12 10:01 ` David Woodhouse
2004-08-12 10:22 ` Marcel Holtmann
2004-08-12 10:35 ` David Woodhouse [this message]
2004-08-12 11:00 ` Marcel Holtmann
2004-08-12 11:33 ` David Woodhouse
2004-08-12 11:49 ` Marcel Holtmann
2004-08-12 12:02 ` David Woodhouse
2004-08-12 12:29 ` Marcel Holtmann
2004-08-12 13:36 ` Marcel Holtmann
2004-08-13 8:07 ` David Woodhouse
2004-08-13 9:05 ` Marcel Holtmann
2004-08-13 9:14 ` David Woodhouse
2004-08-13 11:52 ` David Woodhouse
2004-08-13 12:40 ` Marcel Holtmann
2004-08-12 12:53 ` David Woodhouse
2004-08-13 9:58 ` Marcel Holtmann
2004-08-13 10:56 ` David Woodhouse
2004-08-12 10:10 ` Stephen Crane
2004-08-12 10:25 ` Marcel Holtmann
2005-01-20 14:30 ` David Woodhouse
2005-01-20 14:45 ` Marcel Holtmann
2005-01-20 14:59 ` David Woodhouse
2005-01-20 18:14 ` Marcel Holtmann
2005-01-21 8:26 ` David Woodhouse
2005-01-23 8:12 ` Marcel Holtmann
2005-01-23 11:39 ` Marcel Holtmann
2005-01-23 12:29 ` David Woodhouse
2005-01-23 14:40 ` Marcel Holtmann
2005-01-23 15:11 ` David Woodhouse
2005-01-23 15:22 ` Marcel Holtmann
2005-01-23 23:16 ` David Woodhouse
2004-08-16 9:48 john smith
2004-08-16 10:15 ` Marcel Holtmann
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=1092306935.15466.74.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=daryl@wideray.com \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.