[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1111164: ITP: vkbasalt-cli -- CLI utility and library in conjunction with vkBasalt



On Friday, October 3, 2025 12:14:00 AM Mountain Standard Time Seyed Mohamad 
Amin Modaresi wrote:
> > Your source package currently ships a binary in /usr/bin/ and Python 
modules
> > in /usr/lib/python3/dist-packages/. These should be split out into two
> > different binary packages,
> 
> I think it is not needed, because vkbasalt-cli python lib is not a common
> library, the lib just can be used by vkbasalt-cli not the others

One of the important things in packaging for Debian is that packages need to 
work together in a larger ecosystem and follow established conventions for 
naming and contents.  The established convention for Python packages is that 
all pure Python modules should be shipped in a separate package that begins 
with the python3- (or someday python4-).  These pure Python module packages 
should not install anything into /usr/bin/.  Rather, any executable Python 
code installed in /usr/bin/ should be shipped in a separate package.

I gave you a previous example in the electrum package.  You can also take a 
look at the repositories below.  Let me know if you have problems figuring out 
how to do this.

https://salsa.debian.org/python-team/packages/python-keepkey

https://salsa.debian.org/python-team/packages/python-ckcc-protocol

https://salsa.debian.org/python-team/packages/python-electrum-aionostr

-- 
Soren Stoutner
soren@debian.org

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: