[Pkg-e-devel] Comments regarding ecore_0.9.9.050+svn20081201-1_i386.changes

Nikita V. Youshchenko yoush at debian.org
Sun Jan 4 21:20:22 UTC 2009

> > > Are these -dev package names (e.g. libecore-
> > > really necessary? I mean I can se it for the lib package, but
> > > why the -dev package, too? Do you plan to have multiple
> > > versions of them in the archive simultaniously? Otherwise
> > > versioned build-depends are usually enough.
> >
> > Future API (or ABI) breakages are expected (the same applies to evas,
> > edje and edbus) ...
> I would suggest not encoding the version in the -dev package name,
> since that will force you to add a lot of conflicts relations over
> time.
> It is often acceptable to break the API with new versions of
> a -dev package, since building the reverse dependencies is then
> broken anyway ...

We have discussed this issue before I sponsored the upload.

As far as I understand, non-backward-compatible API changes are expected 
very often, and encoding version into -dev package name is an attempt to 
avoid people (and buildd's) from attempts to build dependant packages 
against "too new" version of -dev package. Such builds already caused much 
pain in the past.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-e-devel/attachments/20090105/be10d370/attachment.pgp 

More information about the Pkg-e-devel mailing list