Op vrijdag 03-10-2008 om 11:17 uur [tijdzone -0300], schreef Marco Túlio Gontijo e Silva:

I noticed that haskell-utils looks in two places to get the package name. update-haskell-control uses the cabal package name and scripts/10/rules uses the information from changelog. I like the idea of querying the cabal name, but I think they should both get it from just one place, to avoid:

dpkg-source -b Cabal-1.4.0.2 dpkg-source: error: source package has two conflicting values - haskell-cabal and haskell-cabal-1.4 dpkg-buildpackage: failure: dpkg-source -b Cabal-1.4.0.2 gave error exit status 255

I know this case is not standard and in cases like this I could edit the generated debian/control file, but still I don't see any reason for getting the package name from two different places.

I noticed that not getting the package name from cabal breaks the dependencies, cause they are generated from the cabal package name. So I think this cabal-1.4 case is very distinct, and it doesn't make sense to change the way haskell-utils generates the package name just because of cases like this.

Greetings.