Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #16725

Re: Existing package splits into dependent subpackages -- best packaging practice ?

From Emmanuel Arias <eamanu@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Existing package splits into dependent subpackages -- best packaging practice ?
Date 2025-02-18 22:20 +0100
Message-ID <KhDay-dEJ-17@gated-at.bofh.it> (permalink)
References <KhBV8-cGY-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi!
On Tue, Feb 18, 2025 at 01:54:19PM -0600, Dirk Eddelbuettel wrote:
> 
> 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?
>
Seems very similar to basemap[0]

[0] https://sources.debian.org/src/basemap/1.4.1-1/
> 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

-- 
cheers,
        Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eamanu@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1                     
 ⠈⠳⣄

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Existing package splits into dependent subpackages -- best packaging practice ? Dirk Eddelbuettel <edd@debian.org> - 2025-02-18 21:00 +0100
  Re: Existing package splits into dependent subpackages -- best  packaging practice ? Emmanuel Arias <eamanu@debian.org> - 2025-02-18 22:20 +0100
    Re: Existing package splits into dependent subpackages -- best  packaging practice ? Dirk Eddelbuettel <edd@debian.org> - 2025-02-18 22:40 +0100
      Re: Existing package splits into dependent subpackages -- best  packaging practice ? Julian Gilbey <julian@d-and-j.net> - 2025-02-23 23:40 +0100
      Re: Existing package splits into dependent subpackages -- best  packaging practice ? Emmanuel Arias <eamanu@debian.org> - 2025-02-25 18:00 +0100
        Re: Existing package splits into dependent subpackages -- best  packaging practice ? Dirk Eddelbuettel <edd@debian.org> - 2025-02-25 18:30 +0100

csiph-web