[Pkg-e-devel] Updated Debian packages for Enlightenment

Andreas Metzler ametzler at bebt.de
Wed Nov 11 18:44:18 UTC 2015


On 2015-11-07 Ross Vandegrift <ross at kallisti.us> wrote:
> On 11/07/2015 01:07 PM, Andreas Metzler wrote:
>> On 2015-11-01 Ross Vandegrift <ross at kallisti.us> wrote:
[...]
>> eolian is experimental, we should not ship it (configure efl with
>> --with-api=legacy).

> Without it we can't build elementary, which means no enlightenment
> either.  I'm not sure if there's enough interest in EFL alone to warrant
> debian packages that can't be used for E!

> Would it be appropriate to consider for experimental?
[...]

Hello,

I think upstream's latests comments (5640E4F7.1030500 at osg.samsung.com
20151110090233.01d21165a702e05a0932c78b at rasterman.com and
5641B465.2090200 at simotek.net) confirms your statement but still looks
reasonably sane. 

We need to make sure that for the time being efl and elementary are
kept in sync, and I *guess* this also holds for the libraries in
efl itself. (e.g. libelocation might use unstable APIs of libeina and
upstream would not consider it a bug to break combining libeina 1.15
with libelocation 1.16)

I have not yet got any very smart ideas, afaict it is not possible to
generate
Depends: libfoo (>= 1.15), libfoo (<= 1.15)
from symbol files.

Perhaps we could use versioned provides/breaks though, with every library
package that needs to be kept in sync having
Provides: libefl-abi (= 1.15.1)
Breaks: libefl-abi (<< 1.15.1)

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



More information about the Pkg-e-devel mailing list