Hey, all, So I was attempting to use cabal-debian to create a package for a library I wanted to check out, but it failed complaining that it didn't know anything about ghc-7.6.2.
Creating a patch to add that information seemed within even my Haskell powers, which I proceeded to do, only to run into the problem that the cabal-debian package won't compile against the haskell-debian package currently in experimental. That turned into a much more extensive patching session, which I later discovered was unnecessary because both packages had been updated upstream. At least I learned a bit. ;) Anyway, ISTM that these should be updated in experimental. I'm happy to try and do this---that said, while I'm fluent in git, I'm a total newbie in darcs. I've read the Darcs intro on the wiki, and I think there are some unstated assumptions that are confusing me, so I wanted to confirm. First, do I understand correctly that the only thing being put into darcs is the debian/ directory? So the .orig.tar.gz and other files exist entirely elsewhere? (This may seem obvious, but I'm used to a git+pristine-tar workflow that keeps everything accessible from git.) So to update a package would involve, say: apt-get source <pkg> cd <src> uupdate ../<new .tar.gz> cd ../<new-src> mv debian debian.updated darcs get darcs.debian.org:/darcs/pkg-haskell/<pkg> <maybe re-run cabal-debian, do any other updates, test build> darcs record -a <build and upload> Does that sound sensible at least? Mike. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
