[tahoe-lafs-trac-stream] [tahoe-lafs] #2063: users expect 'python setup.py install' to install dependencies

[tahoe-lafs]

#2063: users expect 'python setup.py install' to install dependencies
-------------------------+-------------------------------------------------
     Reporter:  sel      |      Owner:  daira
         Type:  defect   |     Status:  assigned
     Priority:  normal   |  Milestone:  undecided
    Component:           |    Version:  1.10.0
  packaging              |   Keywords:  install fedora linux packaging
   Resolution:           |  setuptools
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by gdt):

 I think part of the point of the bug is that user expectations are not
 necessarily right.  There are basically three approaches
  * use a package from a packaging system.  Users should be pointed to this
 as the standard approach.  The overwhelming majority of uses of successful
 programs are like this.
  * run some command from sources and have it go find and install
 dependencies (presuambly only some, and not thing like python!!)
  * read the README, install the dependencies from a packaging system, and
 then build/install.  This is the standard approach for people who are
 going to do development rather than just run.

 My only concern is that the auto-install-dependencies approach is actively
 harmful for packaging systems, because package builds should not use the
 net and should be 100% byte-for-byte repeatable.  So getting dependencies
 should be an explicit step the user has to ask for (perhaps this can be
 hinted at in the error if they aren't there).

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