[Distutils] [Catalog-sig] packaging terminology confusion

[Lennart Regebro]

On Sat, Jan 9, 2010 at 20:17, Suno Ano <suno.ano at sunoano.org> wrote:
>  - *package* means a Python package, (directory intended to be on
>   sys.path, with an __init__.py. We *never* mean a distributable
>   or installable archive, except when “impedance matching” with
>   folks who think in terms of operating system parcels.
>
>  - *parcel* is such a distributable / installable archive:
>   either in source form (an ’sdist’), or one of the binary
>   forms (egg., etc.). Any parcel may contain multiple
>   packages (or even no packages, in the case of standalone
>   scripts).
>
>  - *project* is the process / community which produces releases of
>   a given set of software, identified by a name unique within
>   PyPI’s namespace. PyPI manages metadata about projects (names,
>   owners) and their releases. Every real project has at least
>   one release.
>
>  - *release* is a set of one or more parcels of a project,
>   each sharing the same version. Some PyPI metadata is specific
>   to a release, rather than a project. Every release has at
>   least one parcel.
>
>  - *installer* is an OS specific piece of software provides by
>   some project which usually installs a Python interpreter and
>   other general software in order to have some Python
>   application installed from scratch.

Yes. Again, exactly how I use the words already. This is the same for
all intents and purposes as Tareks proposal, this is how the words are
being used already in practice.

-- 
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64