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

tahoe-lafs trac at tahoe-lafs.org
Mon Aug 26 07:09:30 UTC 2013


#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 sel):

 Replying to [comment:5 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).


 Generally I think the package system just downloads *prebuilt* packages.
 It is okay to have a command line option that must be specified to install
 dependencies, it is also okay to have a list of dependencies that can be
 installed in a separate step.[[BR]]
 My concern is: once I have created the introducer, I need to create N
 storage nodes, that's why I would like to automate the installation as
 much as possible.

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


More information about the tahoe-lafs-trac-stream mailing list