[Tts-project] Migration from Berkeley DB

[Igor B. Poretsky]

Hello,

>>>>> "Samuel" == Samuel Thibault <sthibault at debian.org> writes:

    Samuel> That is it. But that's a common thing to do. And notably on
    Samuel> architectures which can natively run both 32b and 64b
    Samuel> variants. Setting multi-arch tells people they can really
    Samuel> run both versions concurrently.

Thus, the most simple and natural thing to do from my point of view is
to drop out the Multi-Arch field particularly for the rulex-data
package, leaving it untouched for all other binary packages built from
the rulex source.

With Berkeley DB this package did not depend on architecture at all and
could be used concurrently by applications of different
architectures. Now the package itself remains architecture independent,
but it cannot be used by several architectures simultaneously
anymore. And nothing has changed for other binary packages built from
this source.

But is it correct to have Multi-Arch field not for all binary packages
built from one source? Lintian doesn't produce an issue anyway.

Best regards,
Igor.