Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Simon McVittie Newsgroups: linux.debian.maint.python Subject: Re: how to properly split up into python3-foo and foo-util package? Date: Tue, 18 Jul 2023 01:30:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Jul 17 23:25:34 2023 Old-Return-Path: X-Amavis-Spam-Status: No, score=-109.52 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, T_SCC_BODY_TEXT_LINE=-0.01, 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-Disposition: inline X-Debian-User: smcv X-Mailing-List: archive/latest/20968 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/ZLXN1SPdC6xSeGkI@tautology.pseudorandom.co.uk Approved: robomod@news.nic.it Lines: 34 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 18 Jul 2023 00:25:09 +0100 X-Original-Message-ID: X-Original-References: <22369ae5afe61e349375507a47c8945486503182.camel@scientia.org> Xref: csiph.com linux.debian.maint.python:15053 On Mon, 17 Jul 2023 at 23:16:03 +0200, Christoph Anton Mitterer wrote: > How does one know (I guess it must be written somewhere and I just > missed it - or was to lazy to read the relevant section O:-) ) which > one the "current directory" is in which stage of the build? > Or is it simply always ./debian/? All the targets in debian/rules are invoked from the top-level source directory, so relative paths like ./debian/rules will exist. > > I would personally be inclined > > to use something like > > > > usr/lib/python3*/dist-packages/foo > > usr/lib/python3*/dist-packages/Foo-*.egg-info > > This I don't however understand fully. I thought at least the dist- > packages/ intermediate dir would come from pybuild? > > Or is your aim rather at the foo and Foo-*.egg-info? Well for those I > had hoped pybuild would do all possibly necessary checks. I meant the part inside dist-packages. If version 1.0 had the paths I quoted above, but my upstream changes the package so that in version 1.5, it now installs: usr/lib/python3*/dist-packages/foo usr/lib/python3*/dist-packages/bar usr/lib/python3*/dist-packages/Foobar-*.egg-info then those are changes which affect compatibility with other software that depends on this library, and I will need to react to them appropriately in the packaging (and I can update the .install file at the same time). smcv