Hey Francis,
first off, thanks for the quick reply!
Francis Tyers wrote:
They shouldn't be arch specific, although some of them may be PCRE
version specific. I'm not sure why we decided to install them
in /usr/share, but probably because there was no better place.
Could you give more details of which ones appear to differ between
arches and which arches ?
/usr/share is perfectly fine *if* the files are arch-independent. Then
you should make the package declare "Architecture: all" (instead of
any), though.
What I did was download the .deb for various architectures (linked from
packages.debian.org or on your favorite ftp mirror), extracted them with
"dpkg -x foo.deb /tmp/targetdir" and ran diff or diff on the output of
"hexdump -c" of several of them.
I also tried copying the files from other architectures to into place on
my system and it seemed to work.
As such, my conclusion is tentitative as it is only based on experiments
and not on analysis of the format.
If someone with more knowledge about apertium and how these files work
tells you that they are independent of e.g. endianness of integers and
such, I think it is fully believable. I just try not to break your
packages while meddling with them, when you do it yourself, it's a whole
different story. :)
By the way: What are your plans w.r.t. for fixing the
build-dependencies? RC bugs should be closed within two weeks in all but
the most exceptional circumstances (Developer's Reference is very
precise about that), so I was a bit surprised that these were sitting
there...
If you have fixes and your sponsor is busy, I can try to see if we can
find someone to help out if you send and URL with updated packages.
As a final remark, I wonder whether the XML format is stable enough to
rename the development package to not include the version number with
the rationale that it'll break less often than now.
Also, while it is recommendable to build packages using pbuilder or
cowbuilder, it is also a useful exercise to try to run dpkg-buildpackage
in a several times in a row in a directory to see if there are
additional files showing up in diff.gz (that would indicate that you
need to do better cleanup, just as I did). This is mostly a comfort
issue when someone unfamiliar with your package (i.e. me) looks at it...
OK, so this was very straightforward down-to-business talk and
recommendations. Your contribution to Debian is very much appreciated!
Please do not hesitate to ask if you have any questions on the above and
tell me about your plans!
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
