Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Ondrej Novy Newsgroups: linux.debian.maint.python Subject: Re: Separate lib and executable packages? Date: Fri, 07 Feb 2020 13:50:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Feb 7 12:42:11 2020 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.399 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FOURLA=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ondrej-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iak2s0YaZzdgpg97u6clP54Mjmoxmr/okB7Nj44Wgow=; b=Ujpfxp6XeuMvR60Pf6/WyzAtKlQ40JrAbVR3LJmXKMCU4geO3gibtImNr4PBDQYxUi aaB5QG/mq3mrpQPYXhJOeU6AXXu0toFmGbLd/3UBi0NDX13BYbuemA51kUtd1+TYKWNZ h+xicx/wSPdo70VcYkIPE+Lr91VYhK2lOtzXznb6MtIt6V/eDvqTsKlaNpRFzWWLE3Eb 8mZIHeanv+UYSdFKsHklqq7B5Oo5Kj6a8YC/0UBoRgw4M6KN9FekptKRwEO0+cCGR+u2 vmvcU/fBUlaztz5WmdOks6YXJeRoRnXzcoUed2tChD4D/LFcsQEDpmzp/TVUBNz+wzCp fpTA== X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iak2s0YaZzdgpg97u6clP54Mjmoxmr/okB7Nj44Wgow=; b=IRexcOK1gSUtNrkqkSAAOKbqav9y0/JTHPpTyKSdVlE8H0+zAZna1tl0/c7JG2vIDI g5KpT/5aScoeC6AmNO11utRO0kBS7kLjhywBAkpwEU/xBj2UpL6NUkdC89caSvE3nnKU inqNNNb4BGbg6hEmj7cqylOEPAON/Y/sK8kLyNGPZVnXta4rU++xj+AqCGSrouDJd3Ew t4lZDASGmoGWVKyGUe1cN+HVdROgvUsIWRjvrizj/So+Fq3lbc0Kt+JsmbeRG4ieBvle I2wiWkdsRcYJZT4Vl1ZiZuk/i6KV3fRIkxkwpNVrRmAhSbMw6YqoG0zygHzMcQ467YcG 3m9w== X-Gm-Message-State: APjAAAUJ99x7B11V5bSsyHGK3dgiuJjQdm5pRoblPhUsycYt8/YLpijq svdASItFlVG2jEx12FbJIF5y5u9KrQz2i4BWuWavtCYNcgY= X-Google-SMTP-Source: APXvYqy0gPR58uNiIJ6Ij9xoFLLVVFBOCTOkXvO4nCXh+i7kzNvwSTRAAX0ogL+aGZy8UPPmEH0UHNXA7FlOz07aFW8= X-Received: by 2002:a1c:9897:: with SMTP id a145mr4090350wme.132.1581078275203; Fri, 07 Feb 2020 04:24:35 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f4a5da059dfb780b" X-Mailing-List: archive/latest/17901 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAOO6c=xjb8jA2-NWp5+QYusVwDtwhKi_MJSUyeUpwNNGDumN4Q@mail.gmail.com Approved: robomod@news.nic.it Lines: 70 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Fri, 7 Feb 2020 13:24:24 +0100 X-Original-Message-ID: X-Original-References: <20200207113600.fzlk2wzks4hwazfd@emissary.chronitis.net> Xref: csiph.com linux.debian.maint.python:12277 --000000000000f4a5da059dfb780b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, it depends :). My two cents: If you are packaging application (PAPT team): * user is using it in CLI / Xorg * user don't need to know it's written in Python * Python modules are typically private, not usable by other applications/libraries -> one binary package: foo If you are packaging library (DPMT team): * your package is typically not usable by user directly * your package is typically dependency of other packages (Python applications/libraries) -> as many binary packages as "language branches" we have, e.g. python-foo, python3-foo, pypy-foo If you are packaging application with public library part (PAPT team): * both of above * user is using it in CLI / Xorg * BUT package have library part, which can be used in other Python applications/libraries -> as many binary packages as "language branches" we have, e.g. python-foo, python3-foo, pypy-foo + foo for application. "foo" package can contain more than entrypoints, but icons, menu items, ... --=20 Best regards Ond=C5=99ej Nov=C3=BD --000000000000f4a5da059dfb780b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

it depends :). My two cents:

If you are= packaging application (PAPT team):
* user = is using it in CLI / Xorg
* user don't = need to know it's written in Python
* P= ython modules are typically private, not usable by other applications/libra= ries
-> one binary package: foo

If you are pac= kaging library (DPMT team):
* your package = is typically=C2=A0not usable by user directly
* your package is typically dependency of other packages (Python applica= tions/libraries)
-> as many binary packa= ges as "language branches" we have, e.g. python-foo, python3-foo,= pypy-foo

If you are packaging application with public library part (PAPT team):<= br>
* both of above
* user is using it in CLI / Xorg
*= BUT package have library part, which can be used in other Python applicati= ons/libraries=C2=A0
-> as many binary pa= ckages as "language branches" we have, e.g. python-foo, python3-f= oo, pypy-foo=C2=A0+ foo for application. "foo" package can contai= n more than entrypoints, but icons, menu items, ...

--
Be= st regards
=C2=A0Ond=C5=99ej Nov=C3=BD

=
--000000000000f4a5da059dfb780b--