On Thu, Mar 30, 2006 at 11:12:15PM +0900, Carsten Haitzler wrote:
> On Thu, 30 Mar 2006 15:09:32 +0200 Falko Schmidt
> <[EMAIL PROTECTED]> babbled:
> 
> > On Thu, Mar 30, 2006 at 08:53:29AM +0900, Carsten Haitzler wrote:
> > > On Wed, 29 Mar 2006 07:33:08 -0800 "Blake B." <[EMAIL PROTECTED]> babbled:
> > > 
> > > > 
> > > > On Mar 29, 2006, at 1:45 AM, Vlad Alyukov wrote:
> > > > 
> > > > >  EC> changelog.cin ... errr... not right.
> > > > >
> > > > >  EC> do the people doing debian packaging... actually test things?
> > > > 
> > > > There were some half-baked commits just before CVS was taken down.  I  
> > > > hope to clean it up this week and get all packages building for the  
> > > > weekend.
> > > 
> > > ok. i think i might have to poke my finger into it all too - i notice some
> > > totally outrageous "build requirements" (ecore REQUIRES libdiretfb? no -
> > > it's optional and i don't think we should be shipping it as then the final
> > > e install will drag in dfb w2hen actually no apps "use" it - it's there 
> > > for
> > > special case development). also packages need splitting up into more
> > > fine-grained lumps
> > >
> > if there're no objections i'll split libecore0 into the following
> > packages (which will hopefully fix the dependency issues as well):
> > 
> > libecore0
> > libecore0-config
> > libecore0-con
> > libecore0-dbus
> > libecore0-directfb
> > libecore0-evas
> > libecore0-fb
> > libecore0-file
> > libecore0-ipc
> > libecore0-job
> > libecore0-txt
> > libecore0-x
> > 
> > are there packages which can be merged into one?
> 
> i like the split this way. it gives fine-grained control. auto-dependency
> resolving will make sure the right subset is installed.
> 
fine then. i just commited the new .install and control files. hope
everything is alright. if you're not too busy, i'd be glad if you took
a quick look at the dependencies somewhen and tell me if you see any missing
or unnecessary libraries. i grepped the code for #include's and checked
the .so's with ldd and found some missing dependencies in the former
debian control file which should now be fixed.
one more question though: do we need the fonts in data/fonts? i didn't
find any related part which loads fonts. if they're needed indeed,
shouldn't i better make libecore0 depend on the appropriate debian font
package?

> > libecore0-dev will contain all available headers, as it is right now. or
> > should i split that one, too?
> 
> it will have to suck in all the above libs then.
> 
yep, it does.

Falko


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to