From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Upgrade of essential tools libusb dbus systemd
Date: Mon, 25 Feb 2013 22:30:48 +0100 [thread overview]
Message-ID: <1361827848.28061.347.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <512BD5FE.8070900@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2442 bytes --]
Hey Thomas,
On libusb:
There are different versions of this around. You can easily see that we
have libusb-compat and libusbx in IPFire 3:
http://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=libusb-compat/libusb-compat.nm;h=a2c594534d956066dab591feeb7b1f3596bc0178;hb=HEAD
http://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=libusbx/libusbx.nm;h=6394d04577bbbf0de555d727f19c0f2f016e6e28;hb=HEAD
Some packages haven't moved to libusb-1 and I think they will never do
that. So if you need libusb-1, please build libusbx like you find it in
IPFire 3, but keep the older version. There is no need to rename it to
libusb-compat though.
On dbus:
I suppose you could update that, but I cannot see if anything is
actually using it. It's mainly there for building packages which link
against libdbus.
On systemd:
IPFire 2 is in maintainance mode. We do not plan to develop more
functionality and we would like to slowly move to IPFire 3.
I can see that you have a lot of energy in building packages and I like
that. Maybe you can put a bit of that energy into IPFire 3.
-Michael
On Mon, 2013-02-25 at 22:22 +0100, Thomas Ebert wrote:
> How about to upgrade the tools libusb, dbus and systemd to an actual build?
>
> A quick check shows that only a very basic tools on a core installation
> use the shared libraries:
> usb_modeswitch
> linux-gate.so.1 => (0xffffe000)
> libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0xb777b000)
> libc.so.6 => /lib/libc.so.6 (0xb7604000)
> /lib/ld-linux.so.2 (0xb7784000)
> gpg
> linux-gate.so.1 => (0xffffe000)
> libresolv.so.2 => /lib/libresolv.so.2 (0xb770e000)
> libbz2.so.1.0 => /lib/libbz2.so.1.0 (0xb76fd000)
> libreadline.so.6 => /usr/lib/libreadline.so.6 (0xb76ca000)
> libdl.so.2 => /lib/libdl.so.2 (0xb76c5000)
> libusb-0.1.so.4 => /usr/lib/libusb-0.1.so.4 (0xb76bc000)
> libc.so.6 => /lib/libc.so.6 (0xb7545000)
> libncurses.so.5 => /usr/lib/libncurses.so.5 (0xb7528000)
> libtinfo.so.5 => /usr/lib/libtinfo.so.5 (0xb750b000)
> /lib/ld-linux.so.2 (0xb7728000)
>
> AddOn packages with depencies:
> bluetooth
> apcupsd
> usbutils
> v4l-dvb
> nut
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2013-02-25 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 21:22 Thomas Ebert
2013-02-25 21:30 ` Michael Tremer [this message]
[not found] <512BDF0B.80109@gmx.de>
2013-02-26 15:56 ` Michael Tremer
2013-02-26 16:54 ` Thomas Ebert
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=1361827848.28061.347.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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