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
On Mon, Jul 17, 2023 at 10:53:58PM +0200, Christoph Anton Mitterer wrote:
> > >a) Why does it work to use just usr/... and not
> > debian/tmp/usr/... ?
> > > Actually, both seems to work, which confuses me even more ^^
> > You can check the search logic in dh_install(1).
>
> Well I have
On Wed, 2023-07-12 at 02:21 +0200, Simon McVittie:
> >a) Why does it work to use just usr/... and not
> debian/tmp/usr/... ?
> > Actually, both seems to work, which confuses me even more ^^
>
>From debhelper compatibility level 7 on, dh_install will fall
> back to
>
Hey.
Sorry for the delay. I'm not subscribed to the list and forgot
mentioning to keep me on CC. ^^
On Wed, 12 Jul 2023 11:19:07 +0200, Andrey Rakhmatullin wrote:
> I don't think there is, and I don't think "usr/bin stuff should
> likely go
> in the other". Many Python module packages ship
On Wed, 12 Jul 2023 11:05:57 +, c.bu...@posteo.jp:
> Do you have a link to your repository?
I'm afraid it's not (yet) publicly available. The whole thing started
out as a poorly written set of shell scripts 10 years ago and I finally
got my act together to re-implement it in Python.
It
On Wed, Jul 12, 2023 at 11:56:05AM +, c.bu...@posteo.jp wrote:
> > > You build two Debian packages (deb-files) out of one source tarball?
> > > Interesting to know that this is possible.
> > It's definitely possible and I would expect any good guide to mention
> > this.
>
> I really need to
Am 12.07.2023 13:25 schrieb Andrey Rakhmatullin:
On Wed, Jul 12, 2023 at 11:05:57AM +, c.bu...@posteo.jp wrote:
You build two Debian packages (deb-files) out of one source tarball?
Interesting to know that this is possible.
It's definitely possible and I would expect any good guide to
On Wed, Jul 12, 2023 at 11:16:28AM +0100, Simon McVittie wrote:
> On Wed, 12 Jul 2023 at 11:19:07 +0200, Andrey Rakhmatullin wrote:
> > I don't think "usr/bin stuff should likely go
> > in the other". Many Python module packages ship executables, especially
> > now that you no longer have Python 2
On Wed, Jul 12, 2023 at 12:16:51PM +0200, Gregor Riepl wrote:
> > > 5) Not really 100% Debian related, but in the Python sdist,... should
> > > that contain the debian/*?
> > No, and the upstream source shouldn't contain debian/ anyway, as the life
> > cycles of packaging and upstream sources
On Wed, Jul 12, 2023 at 11:05:57AM +, c.bu...@posteo.jp wrote:
> What do you mean by the terms "simple Python package" and "two packages"?
> These terms do not exists in Python context.
These are Debian terms.
> Python do differentiate between
> "Distribution Package" (the name you would find
Dear Christoph,
I'm sure I can not help you but I'm asking because I want to learn.
Do you have a link to your repository?
What do you mean by the terms "simple Python package" and "two
packages"? These terms do not exists in Python context. Python do
differentiate between "Distribution
5) Not really 100% Debian related, but in the Python sdist,... should
that contain the debian/*?
No, and the upstream source shouldn't contain debian/ anyway, as the life
cycles of packaging and upstream sources should be separate even if the
person doing both is the same.
This would then
On Wed, 12 Jul 2023 at 11:19:07 +0200, Andrey Rakhmatullin wrote:
> I don't think "usr/bin stuff should likely go
> in the other". Many Python module packages ship executables, especially
> now that you no longer have Python 2 subpackages.
I would personally say that if the executables are
On Wed, 12 Jul 2023 at 02:21:48 +0200, Christoph Anton Mitterer wrote:
> 2) I then tried with such package.install files like those:
>foo-util.install:
> usr/bin
>
>python3-foo.install:
> usr/lib
>
>a) Why does it work to use just usr/... and not debian/tmp/usr/... ?
>
On Wed, Jul 12, 2023 at 02:21:48AM +0200, Christoph Anton Mitterer wrote:
> When I run debuild -us -uc on that, it generates:
> debian/tmp/...
> debian/tmp/usr/bin/
> debian/tmp/usr/lib/python3.11/dist-packages/foo
> debian/tmp/usr/lib/python3.11/dist-packages/foo-1.0.0.dist-info
>
Hey.
Maybe someone can help me with the following:
I have a little Python project that uses setuptools or packaging. Only
with pyproject.toml, no setup.py or so.
pyproject.toml specifies the build-dependencies like so:
[build-system]
requires = ["setuptools>=61.0.0",
16 matches
Mail list logo
