[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Rewritten html_reports



I felt like working on lintian today, but since the Subversion repository
is temporarily down (I'm sure Jeroen will get to it when he gets a chance;
it's the holidays), it was a good day for a fairly large project rather
than bug catchup.

I now have a rewritten html_reports that hasn't been tested yet but which
is almost finished.  Among the new features:

* Uses Text::Template and external templates for all of the web pages,
  which should make it easier to make cosmetic changes, add better style
  sheets, and so forth.

* HTML pages don't have HTML problems like <h2> before <h1> and should
  have somewhat better formatting.  I'm experimenting with not wrapping
  the tags in <pre> and we'll see how that goes, but it's easy to change
  back if we need to.

* Each maintainer page now has a regular page, showing only errors and
  warnings as now, and a full page which includes info, experimental, and
  overridden tags.

* All tags now have tag pages, including info-level tags and tags that
  only show up in the archive as overrides.

* If a binary package has a different version than the source package,
  that will now generate a separate section with the binary package
  version on the maintainer page, to make it clearer when lintian reports
  might lag due to missing i386 builds.

* Multiple maintainers with the same e-mail address don't overwrite each
  other's lintian report pages.

* Anchors for packages with dashes in the name now use the dashes in the
  anchors.  The XHTML standard explicitly says - is an allowed character
  in anchors, so I think the transformation was unnecessary.  This makes
  it easier to link to specific packages.

* The tag index page also includes, next to each tag, the number of times
  it's been overridden.  This should make it easier to figure out what
  tags in lintian need work so that maintainers don't have to override
  them so often.

Work that remains:

* Testing, of course.

* Add a co-maintained package list to each maintainer's page.  I think I
  now see how to do this easily in the new structure, although it also
  requires changes to the list format and some of the other files.

I don't have anything up yet for people to look at (no testing yet), but I
wanted to let people know so that no one spends time working on the same
thing.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>


Reply to: