Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Dirk Eddelbuettel Newsgroups: linux.debian.maint.python Subject: Existing package splits into dependent subpackages -- best packaging practice ? Date: Tue, 18 Feb 2025 21:00:02 +0100 Message-ID: X-Original-To: debian-python X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Feb 18 19:54:37 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-109.349 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.34, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MURPHY_FINANCE10=0.5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: VM 8.2.0b under 29.4 (x86_64-pc-linux-gnu) X-Debian-User: edd X-Mailing-List: archive/latest/22827 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/26548.58731.571734.173421@rob.eddelbuettel.com Approved: robomod@news.nic.it Lines: 27 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Dirk Eddelbuettel X-Original-Date: Tue, 18 Feb 2025 13:54:19 -0600 X-Original-Message-ID: <26548.58731.571734.173421@rob.eddelbuettel.com> Xref: csiph.com linux.debian.maint.python:16722 Hi all, I have long maintained rpy2 (and rpy before) which provides a bridge from Python to R (which I tend to care more for), and am on friendly terms with its author. You can see my repo at salsa [1], it is pretty vanilla. The upcoming upstream release will split into three packages, all in the same source repo [2]. I am a casual Python user, and not all into packaging there (source or for Debian). But I can wondering that this arrangement must exist elsewhere. Is there a good pattern I can borrow to build (and then install ?) rpy2-interfaces to then build (and install ?) rpy2-objects to then build rpy2? Python users see these as independent as they are in three different PyPI packages. Is there a best or recommended way to approach this? CCs welcome, I am not subscribed to debian-python. Cheers, Dirk [1] https://salsa.debian.org/edd/rpy2 [2] https://github.com/rpy2/rpy2 -- dirk.eddelbuettel.com | @eddelbuettel | edd@debian.org