On Mon, 18 Aug 2014 23:51:43 +0200 Pietro Abate <pietro.ab...@pps.univ-paris-diderot.fr> wrote:
> Hei Sven, > > On 18/08/14 18:10, Sven Bartscher wrote: > > If we have a package, which doesn't migrate to testing, we usually > > check the "Why does package X not in testing yet?" page or the PTS. > > Usually they do a great job in telling us why our package doesn't > > migrate. > > > > But sometimes you have packages, which have complicated dependencies, > > that don't make it easy to tell why our package doesn't migrate. > > Usually the PTS and "Why is package X not in testing yet?" fail at > > those packages and don't give any useful explanation. For example look > > at the page for haskell-hgettext[1]. > > you might want to have a look at comigrate [1] a tool designed to > answer these kind of questions and provide explanations that are as > compat as possible. For example for haskell-hgettext [2] . If you find > it useful, I'm sure the authors would be happy to hear from you. I looked at it and it's a great tool to identify problems with migrations, but it's not really what I was aiming for when I wrote my tool. The web interface does list that haskell-src-exts needs to migrate, which is right, but not really helpful. To find the root causes of the problem I need to navigate through all the packages with their own listings. If my browser wouldn't mark links I already visited I would have a great chance to end up in a loop. So it's just too much data to understand what's the problem and what to do against it. The command line interface couldn't provide as much information. It follows the dependency chain until it ends up at pandoc and doesn't know what to do. My tool (which still doesn't have a name, suggestions welcome) has another approach of identifying the problem. Instead of checking dependencies it checks for the autohint the package in question is in. So instead of searching for the relevant information itself, it takes a huge amount of information and filters it for the useful informations. Wile this approach gathers more relevant information than other tools (I know), I still don't know if it identifies all issues a package might have. So in conclusion: comigrate is a really nice tool. But, as far as I know, it's not really suitable to analyse transitions, as big as haskell transitions. Regards Sven
signature.asc
Description: PGP signature
