Re: [Ltib] New packages in Ltib

[Stuart Hughes]

Hi Luis,

Thanks for your contribution.  I'm busy with the day job at the moment,
but will look at this as soon as I can in more detail·

As far as exporting PKG_EVAS etc goes, I'd prefer not to export all
PKG_*.   What are you trying to get at with these, is it the versions or
just to see if they're enabled?

If you want the versions you can do things like this inside the spec
file:

    _py_ver=$(rpm --dbpath %{_dbpath} -q python | \
        perl -n -e 'm,python-(\d+\.\d+), and do { print $1 }')


If you just want to test if a package is installed in ltib (for example
python) you could do:

if rpm --root `pwd`/rootfs -q python &>/dev/null; then echo installed; fi

Regards, Stuart

On Tue, 2008-09-09 at 18:28 -0300, Luis Felipe Strano Moraes wrote:
> Hi,
> 
> attached are .spec files and the necessary changes for pkg_map and 
> packages.lkc
> for the following new packages :
> - SQLite
> - Ecore
> - EDB
> - Edje
> - Eet
> - Embryo
> - Emotion
> - Evas
> - Expedite
> - Light Media Scanner
> 
> The tarball for SQLite can be found on its own site. The others have a
> dist target on the
> makefile that generates a tarball for you (provided you have already
> checked them out
> from svn/git and ran autogen.sh), but I can provide tarballs with
> corresponding md5 hashes
> if anyone wants it.
> 
> Also, in order to build correctly, the following variables should also
> be exported by
> setup_env_vars inside ltib itself : PKG_EVAS, PKG_GSTREAMER_CORE and PKG_EET.
> I believe that a better approach than exporting specific variables
> would be to export
> the entire PKG_ namespace or something like that.
> 
> Any comments are welcome.
>