Hi,
On 26/09/2025 09:27, Aryan Karamtoth wrote:
On 26/09/25 11:46, Jerome BENOIT wrote:
Hi,
On 26/09/2025 07:06, Aryan Karamtoth wrote:
Hi,
I'm currently writing some software in C that I'd like to package into Debian
once its stable enough. I've gone through the teams wiki [1] and I noticed that
there isn't a team that maintains software written in C or command line tools
in general.
I'm confused about which team i should choose to maintain my software with. For
context its a minimal package manager for C.
This has been discussed a little bit on #debian-mentors yesterday and I was told that
"software written in C or general command line tools" is a bit too generalised
to fit into a X team.
I'd like some advise in this situation.
Can you tell us more about your software ?
What is its purpose ? Is it a scientific software ? a system administrative one
? an editorial one ? ...
Plus, I also need some advice on which debhelper to use for lintian and
packaging since my software uses GNU make for building.
If you have a working autotools set up to build your software,
the packaging with debhelper tools should be straightforward
providing you follow linux/GNU traditional conventions.
Having said that, this webpage https://wiki.debian.org/Packaging might be a
good start.
hth,
Jerome
[1] https://wiki.debian.org/Teams
my software is named covers. It's an experimental software of mine thats a
package/library manager for C.
I am afraid there a lot of well established tools to do that,
for instance the GNU autotool suites (autoconf, automake, libtool, make, ...)
and cmake.
Furthermore, it might be far more challenging that you think because such a
package might work
on different platforms, and this goes beyond C.
I'm writing it to get better at C but I thought it'd also be good for
practical use if I develop it further.
https://codeberg.org/covers/covers
It's currently barebones at the moment (v0.1.0 was written in a week) and I'd
like to get it to a much more usable state before distributing it on debian. I
hope to do this before forky's freeze but I don't know if I can finish it in
the intended time.
It's a CLI tool so I thought there's some team where I could discuss and get
help with the packaging once I develop it further.
CLI is the rule in GNU/Linux not the exception, so it is a far too generic
theme for a dedicated team.
As of v0.1.0 covers only uses GNU Make and C. I like to keep it this way as
much as I can.
You might consider the (GNU) autotool suite (which includes make).
hth,
Jerome
