[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2049: Decide where "packaging tests" should live.

[Tahoe-LAFS]

#2049: Decide where "packaging tests" should live.
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  nejucomo
  nejucomo               |     Status:  new
         Type:  task     |  Milestone:  soon (release n/a)
     Priority:  normal   |    Version:  1.10.0
    Component:  dev-     |   Keywords:  packaging dev-infrastructure
  infrastructure         |  buildbot pypi openitp-packaging
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by nejucomo):

 Replying to [comment:21 Zancas]:
 >

 ...

 Zancas and I are chatting in realtime and we both agree that having clear
 terminology could help avoid confusion.

 As an example, in the **Inputs** section, first bullet, I say "build", but
 what I means is *not what* {{{python ./setup.py build}}} does.

 In fact, all of this description kind of ignores what {{{python ./setup.py
 build}}} does, which is kind of a "local compilation and install without
 creating any package".

 Other sources of confusion:

 "distribution" - does this mean the process of copying bytes from some
 "package repository" onto a local system and then installing it?  *-or-*
 does it mean "linux distro" or does it mean the format of the bytes in a
 package or what?

 "packaging" - Is this the process of converting source code into a package
 file (tarball, ``.whl``, ``.deb``, ``.dmg``, etc...)?  Is it the process
 of publishing such files to "package repositories"?  Is it the process of
 installing?


 I propose we focus on the checklist in ticket:2049#comment:15 and ignore
 the description *for now*.   Later we can categorize the different tests
 we create and create a canonical lexicon.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2049#comment:23>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage