Re: [Ltib] New packages in Ltib

[Luis Felipe Strano Moraes]

I know I'm kind of flooding the list with packages, but here are a few more :
- efreet (another one from efl)
- enlightenment (which depends on the X.Org ones I sent earlier)
- libXext
- libXrender (these were requirements for enlightenment

There are two notes worth mentioning :

1) There's a need for native versions of eet and edje to be available
on the PATH in order to build some of the enlightenment packages,
where could this be specified ?
2) The libX11 package I sent earlier did not compile because it needs
to compile natively one utility called makekeys. I "fixed" that by running
the src/util makefile separately with clean PATH, and then running make
for the rest of the package. I tried instead of changing the PATH variable
to specify the gcc compiler directly, but then it tries to call the
gnu assembler
from the cross-toolchain and changing GCC_EXEC_PREFIX incurred into alot
of errors. Is there any other (better) way of fixing this ? I'm sending the new
version attached here so there's at least a working version in here.

--lf



2008/9/17 Stuart Hughes <address@hidden>:
> Thanks, I'll try to get to it as soon as possible.
>
> Regards, Stuart
>
> On Tue, 2008-09-16 at 15:39 -0300, Luis Felipe Strano Moraes wrote:
>> 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

efreet.spec
Description: Binary data

enlightenment.spec
Description: Binary data

libXext.spec
Description: Binary data

libXrender.spec
Description: Binary data

libX11.spec
Description: Binary data