[pkg-fso-maint] [Pkg-e-devel] pkg-e stack update for freerunner?
Nikita V. Youshchenko
yoush at debian.org
Sun Feb 22 08:03:00 UTC 2009
> > > > > Indeed, I finished pushing everything to git yesterday, although
> > > > > I haven't tagged them for upload yet
> > >
> > > source packages now available in
> > > http://alioth.debian.org/~lutin-guest/sources/2009/
> > I will build armel packages for freerunner.
> In evas/debian/control, you forgot to rename libevas-0.9.9.050a-engines
> and libevas-0.9.9.050a-engines-extra to their 0.50b equivalents.
Although I see this is strictly not necessary...
But I was not necessary to rename libevas-engines to
libevas-0.9.9.050a-engines as well, because renaming pf libevas package is
enough to handle binary-incompatibility hell, dependences will do the
I still thing it is ugly to have libevas-0.9.9.050b together with
We should rename back to libevas-engines, or rename to
Using unversioned libevas-engines name may be better because other packages
have to depend on it, so versioned libevas-engines name makes maintaince
of those a bit harder (e.g. have to fix debian/control instead of just
What do you think?
I've stopped rebuilding pkg-e things for pkg-fso until this is resolved, to
avoid pkg-fso having package naming different from what will be in debian.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090222/3acf8b05/attachment.pgp
More information about the pkg-fso-maint