[Pkg-e-devel] pkg-e stack update for freerunner?

Albin Tonnerre albin.tonnerre at gmail.com
Sun Feb 22 10:32:48 UTC 2009


>
> 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
> rest.
>

> I still thing it is ugly to have libevas-0.9.9.050b together with
> libevas-0.9.9.050a-engines.
> We should rename back to libevas-engines, or rename to
> libevas-0.9.9.050b-engines.
>

I did the latter yesterday. You might be interested in subscribing to
pkg-e-commits [1], it's relatively low-traffic and that probably would make
it easier for you to track changes.


>
> 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
> rebuild).
>
> What do you think?
>

I completely agree. In fact, I was about to make the same proposal. I'll do
the changes today

Regards,
Albin

[1] http://lists.alioth.debian.org/mailman/listinfo/pkg-e-commits
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-e-devel/attachments/20090222/014cf89b/attachment.htm 


More information about the Pkg-e-devel mailing list