Matthias Klose writes:
>
> This is somehow useless. It may work for the 32/64 bit case, but not when
> installing it to do cross builds.
Why not?
>
> datefudge is used as a b-d for gnutls26 and gnutls28. And what I do
> understand,
> it runs on the build, not on the host. Therefore it has to be M-A foreign.
>
> If you want to have the library installable in parallel, then split it out
> into
> a separate lib package and make it M-A same.
To be honest I don't understand why having an `Arch: all, M-A: foreign'
package depending on version =${source:Version} of `Arch: any, M-A:
same' lib package would be better than having just one `Arch: any, M-A
same' package. What's the difference?
Please note that datefudge is quite a small package, I would like to
avoid splitting it into yet smaller ones without a really good reason.
> Also, why is an extra private
> shared library dir needed for this package?
I thought that globbing /usr/lib/datefudge/*-*-*/datefudge.so (see line
50 of /usr/bin/datedufge)
would have better performance that globbing for
/usr/lib/*-*-*/datefudge/datefudge.so. The difference probably is not
even noticeable, so I can change it in next version.
Regards,
robert
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
