Hi Riku, Am Montag, den 07.11.2011, 13:36 +0200 schrieb Riku Voipio: > Package: hscolour > Version: 1.19-1 > Severity: normal > > haskell-devscripts depends on hscolour, while hscolour build-depends on > haskell-devscripts. with force-depends installed haskell-devscripts, > hscolour builds fine. So it appears not all funtionality of haskell-devscripts > depends on hscolour. > > This could be solved by > > 1) making hscolour not build-depend on haskell-devscripts. > 2) splitting haskell-devscripts to two packages, one with the hscolour using > scripts, one with rest scripts.
we are considering to add hscolour as a Build-Dependency to ghc even... The current setup works fine for everyone but those bootstrapping a new architecture. For those few, I find it reasonable to expect them to do what you did, e.g. force-install haskell-devscripts (or ghc, once it build-depends on hscolour). Things would be easier if aba’s proposal about Build-Depenes-Stage1 or however it will be called will be implemented. Where would you, as a porter, first look for information about breaking such cycles? README.source? Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
