[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9419 [TorDNSEL/TorBEL]: update tordnsel to work with debian wheezy ghc libs
#9419: update tordnsel to work with debian wheezy ghc libs
---------------------------------+-------------------
Reporter: phobos | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: TorDNSEL/TorBEL | Version:
Resolution: | Keywords:
Actual Points: | Parent ID: #9417
Points: |
---------------------------------+-------------------
Comment (by dkm):
Replying to [comment:28:ticket:9204 phobos]:
> Can you do a set of patches against the canonical tordnsel repo at
https://gitweb.torproject.org/tordnsel.git ?
Attached.
Let's get this one out, then I'll post another batch to fix a bunch of
deprecation errors left.
> once I can merge the changes, we can release a new version, and try it
out on our server. can everything be installed via apt-get? We can't do
cabal on production machines, only apt-get. If it's not in a debian repo,
we cannot install it.
Cabal is haskell's build infrastructure; you use it to compile regardless
of whether you invoke the `cabal` binary or the `Setup.hs` scriptlet.
re: debian repo:
I added some additional code to cope with relatively old libraries in
wheezy (so it builds exactly with libghc-XXX-dev libraries installed with
apt), but it will break the build the next time libraries are revbumped.
Cabal can also fetch and compile all the needed haskell dependencies for a
project. What's your take on having build-time deps that are ''not'' in
debian repos, but are fully automatically fulfilled by the build system to
produce a debian-packagable and deployable binary?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9419#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs