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


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

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

From Dirk Eddelbuettel <edd@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Existing package splits into dependent subpackages -- best packaging practice ?
Date 2025-02-25 18:30 +0100
Message-ID <Kk6UN-1Vwy-3@gated-at.bofh.it> (permalink)
References <KhBV8-cGY-5@gated-at.bofh.it> <KhDay-dEJ-17@gated-at.bofh.it> <KhDtT-dLC-5@gated-at.bofh.it> <Kk6rL-1V6X-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Emmanuel, (and also Hi! to Julian whom I owe a follow-up too),

On 25 February 2025 at 13:55, Emmanuel Arias wrote:
| On Tue, Feb 18, 2025 at 03:37:37PM -0600, Dirk Eddelbuettel wrote:
| > I may have been unclear in what I was looking for.  If I read this correctly,
| > then it "bends" the upstreeam layout to effectively undo the package split?
| > 
| > I was thinking more along the lines of 'how do I create three binary Python
| > packages that are interdependent from one source repo'. Is that doable?
| > 
| I've forgotten the python-deadlib case. It is one upsream source
| repository and 12 binary packages from different folders from upsream.
| Maybe that you was looking?

Oh that looks very good. From a glance at debian/control some of these have
interdependencies too.  Ie python3-standard-aifc depends on
python3-standard-chunk which is the para in front of it. And debian/rules is
admirably simple.  That may work.  Then again the directory layout is a
little different because they are all 'sibblings'.

But as I have only three package, with the (old) "outer" package and two it
needs as top-level directories in the main repo, maybe I can just line up the
commands as per deadlib's loop.

I am still mighty confused about how to (normal) install step will pick up
the directories ... but the penny just dropped:  as per the *.install files
as you have it here. That could actually work.  Yay.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | edd@debian.org

Back to linux.debian.maint.python | Previous | NextPrevious 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