Re: lintian: add classification tags for packages that need porting to different architectures?
Paul Wise dixit:
>Any thoughts?
What’s the use? (In the good sense, a pure question out of interest.)
For example, there’s software that upstream is written in a way to
only work correctly on little-endian platforms, e.g. because its file
parser doesn’t do letoh32() and friends. These need large changes,
but upstream (and, then, perhaps the source code is, for example,
commented in, and uses variable names in, French… *shudder*).
OK, so the distro’s data may give people an idea where to work on.
It may also lead to duplicated investigative efforts.
Perhaps something like repro-builds have, a repository with notes
on individual packages, where people who once investigated one thing
could note this down, and which interested porters would use as the
main entry point *instead of* the raw lintian stats, would be useful?
You could then mechanically create files in that repo for packages
which show up in lintian but don’t have such notes yet, to signal
that they show up.
Just my “five minutes of thinking about this”, nothing deep.
bye,
//mirabilos
--
<ch> you introduced a merge commit │<mika> % g rebase -i HEAD^^
<mika> sorry, no idea and rebasing just fscked │<mika> Segmentation
<ch> should have cloned into a clean repo │ fault (core dumped)
<ch> if I rebase that now, it's really ugh │<mika:#grml> wuahhhhhh
Reply to: