Re: [tor-bugs] #8506 [Ooni]: Provide OONI packages for Debian

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#8506: Provide OONI packages for Debian
------------------------+----------------------
     Reporter:  lunar   |      Owner:  lunar
         Type:  task    |     Status:  accepted
     Priority:  normal  |  Milestone:
    Component:  Ooni    |    Version:
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+----------------------

Comment (by aagbsn):

 Replying to [comment:23 lunar]:
 > Replying to [comment:22 aagbsn]:
 > > The ooniprobe.conf.sample is read from /usr/share/ooni into the users
 > > home directory as ~/.ooni/ooniprobe.conf (where the user can edit it)
 > > upon instancing the ooni configuration object at runtime (if that
 directory
 > > and file does not already exist).
 >
 > Ok, perfect. :) Maybe the `.sample` suffix is what confused me. I would
 probably
 > not had doubts if it was `.defaults` instead or something similar.
 >
 > > The default value for option "data_dir" is /usr/share/ooni/, which is
 not user writable. If we add a command (post installation) to download the
 GeoIP data, we would also need to change the default path in the config
 file, and each user on a shared system would need their own copy of (not
 version controlled) GeoIP data. Meh.
 >
 > So we both agree that post-installation is bad (installing the
 `Makefile` is also post-installation). How about a better pre-installation
 mechanism?
 >
 > In any cases, not installing the `Makefile` is good enough from the
 Debian package point of view. By policy, building Debian packages cannot
 use the network anyway, so it is the role of the package maintainer to
 manually download and add these archives to the package source. It is
 already implemented in the current package source.

 I can remove the Makefile from the MANIFEST.in
 >
 > I don't know about `pip` or other installation methods, but yeah, you
 might want to distribute those files in source tarballs like the Debian
 package currently does.

 So, I am not clear on whether we decided to bundle the geoip files with
 ooniprobe or not. If we do that, I shall update the LICENSE accordingly.

 pygeoip is definitely not compatible with tor-geoipdb. Unclear whether
 it's worth hacking support for tor-geoipdb at this point. It does look
 like the maxmind database is available as a deb (geoip-database), but only
 at the country level (and we also want the city and asn level databases).

 Perhaps we should add the remaining databases as packages too?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/8506#comment:24>
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