ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] New packages in Ltib


From: Luis Felipe Strano Moraes
Subject: Re: [Ltib] New packages in Ltib
Date: Tue, 16 Sep 2008 15:39:55 -0300

New versions of the following packages :
- ecore
- emotion
- evas
- expedite

Also, I changed cairo.spec to stop using PKG_DIRECTFB and start
using rpm to query the database.

--lf


2008/9/10 Stuart Hughes <address@hidden>:
> 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.
>>
>
>
>



-- 
Luís Felipe Strano Moraes
ProFUSION embedded systems
http://profusion.mobi

Attachment: cairo.spec
Description: Binary data

Attachment: ecore.spec
Description: Binary data

Attachment: emotion.spec
Description: Binary data

Attachment: evas.spec
Description: Binary data

Attachment: expedite.spec
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]