[tahoe-lafs-trac-stream] [tahoe-lafs] #1717: 'sudo make install' doesn't work

[tahoe-lafs]

#1717: 'sudo make install' doesn't work
----------------------------+--------------------------------
     Reporter:  davidsarah  |      Owner:  warner
         Type:  defect      |     Status:  new
     Priority:  major       |  Milestone:  undecided
    Component:  packaging   |    Version:  1.9.1
   Resolution:              |   Keywords:  setuptools install
Launchpad Bug:              |
----------------------------+--------------------------------

Comment (by warner):

 Yeah, I'm ok with removing "make install", as long as packagers aren't
 using it.

 The original idea with "make install", which existed long before we
 started using setuptools, was to make traditional autoconf/unix-style
 build/install commands work. In that world (my homeland, you might say)
 "make; sudo make install" is all you need to put things in the right
 place. And "make install PREFIX=/xyz" was the right way to install it
 somewhere other than /usr/local, which was convenient for packagers (where
 /xyz was usually ./temp-pkg-dir and got tarred up and turned into a
 distribution package).

 That PREFIX=/xyz didn't work with "setup.py install" once setuptools came
 to call, because it insists upon the installation directory already being
 in your PYTHONPATH, and also installed that weird .pkg-info metadata (at
 least I considered it weird at the time). So I added those extra flags to
 the Makefile both to remind myself of what they were, and to allow "make
 install PREFIX=" to be useful to packagers that wanted the traditional
 interface.

 If our packagers are all using setuptools-native commands (some form of
 {{{setup.py install}}} that points to a local directory), then we can
 remove the "make install" target. The current ubuntu packaging
 (http://archive.ubuntu.com/ubuntu/pool/universe/t/tahoe-lafs/tahoe-
 lafs_1.8.3-2.debian.tar.gz) appears to use this:

 {{{
 python setup.py install \
  --no-compile --install-layout=deb \
  --single-version-externally-managed \
  --root $(CURDIR)/debian/$(package)
 }}}

 (i.e. what 'make install PREFIX=' used to do). So they won't be affected.
 We should check with the other packagers to make sure this won't impact
 them, but if so, they should really switch to the ubuntu scheme.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1717#comment:5>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage