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 -- you introduced a merge commit│ % g rebase -i HEAD^^ sorry, no idea and rebasing just fscked │ Segmentation should have cloned into a clean repo │ fault (core dumped) if I rebase that now, it's really ugh │ wuahh
lintian: add classification tags for packages that need porting to different architectures?
Hi all, I had the idea to add a series of lintian classification tags that will assist porters in finding packages that need fixes for their port. The current set of ideas for these tags include: * list arches that don't match Architecture in debian/control * list arches that don't match Architecture in debian/tests/control * list arches where debian/rules checks DEB_HOST_ARCH * list arches where debian/rules mentions the arch name at all * list arches where C source code references other per-arch defines but does not mention the defines for the current arch One important thing for these tags is that they be possible to query on a per-architecture basis, so that porters who care only about specific architectures can find packages that need porting to those arches. Currently UDD doesn't allow this but it should be easy to add. While some of the potential tags are possible to implement manually just using local grep-dctrl | dpkg-architecture commands, it would be useful for some teams, especially those new to Debian, to be able to just link to a precomputed list of packages for each architecture. Also some of the above ideas for these types of classification tags won't be possible to easily implement manually without a local mirror. The Debian ports infra, sysadmin, archive admin and release teams may also want to use the computed stats for determining the eligibility of individual ports for the different architecture support levels. Once these tags are created, I'll link to them from these pages: https://wiki.debian.org/PortsDocs/New#Other_work https://wiki.debian.org/PortTemplate Any thoughts? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
