Re: [Ltib] Trying to upgrade bluez - tripping over LTIB

[Stuart Hughes]

Hi Peter,

LTIB does auto-complete package names for you (by looking in the spec files
and matching the name).  To defeat this rather than saying:
./ltib -p pkg say: ./ltib -p spec_file_name, for example
./ltib -p bluez.spec

BTW: rather than create a new package name, if you want a newer
version, it's better to create for example bluez-utils-4.33.spec
and the build it by hand with: ./ltib -p bluez-utils-4.33.spec.
Later on you can add a entry in your platform's pkg_map to set
this version as the default in for your package.

For those more familiar with bluez, do you think it's worth
upgrading this for all platforms? the reason for the older
one was to avoid the need for dbus (extra space etc), but
we could add dbus.  I'm open to ideas/comments/opinions.

Regards, Stuart

--- address@hidden wrote:

From: Peter Barada <address@hidden>
To: "address@hidden" <address@hidden>
Subject: [Ltib] Trying to upgrade bluez - tripping over LTIB
Date: Mon, 23 Mar 2009 13:37:30 -0400

I'm trying to upgrade to a newer version of bluez, and in the 4.33
version, the utilities and libraries are apparently merged.

1) copied dist/lfs-5.1/bluez/bluez-utils.spec to
disk/lfs-5.1/bluez/bluez.spec

2) modified it:
   - change Name: to "bluez"
   - change Version: to "4.33"
   - stripped out Patch1.

3) I added to config/userspace/packages.lkc an entry for PKG_BLUEZ

4) Added "PKG_BLUEZ = bluez" to config/userspace/pgk_map

5) Added "PKG_BLUEZ=y" to config/platform/.../.config

Now when I try to do "./ltib -p bluez -m prep", LTIB happily remaps
"bluez" to "bluez-libs", even though I've turned off PKG_BLUEZ_LIBS
in .config, defconfig.dev, and defconfig.  If I specify the full name
(as in "bluez.spec"), it works, but that won't work when I let LTIB
build through "./ltib".

I have a feeling LTIB is trying to be helpful here(by auto-completing
the spec name?), but how can I work around this?

-- 
Peter Barada <address@hidden>