Hi,

Thusly spoke Daniel Reurich (daniel@??? on 2017-10-20
12:18 +1300):
>
> There is no reason to set an epoch at all.
>
> the package should not build or ship libudev... but libeudev and have:
> "Provides: libudev1 (=<libudev version>)
> "Replaces: libudev1
>

I'm ambivalent about whether we ship libudev or libeudev. Both can be
argued for:

- we ship a library from the source package eudev
- we ship a library called libudev.so

The advantage of shipping a libudev package means that it can serve as
a drop-in replacement, and we don't have to worry about anything else.
The epoch also makes sure that the Debian libudev will never be
installed if someone mixes releases, because our version is always
higher.

The advantage of shipping libeudev with a Provides: on libudev1 is
that we can declare the exact libudev version we are compatible with
(which is libudev1 (= 215) at the time of the fork). This not only will
be more correct, it will also prevent users from installing packages
that expect a newer libudev version than we have.


Regards,
tremon