#1071126 ITP: battinfo -- cli tool & nim-lang library to query battery info for GNU/Linux

Package:
wnpp
Source:
wnpp
Submitter:
Prasanna Venkadesh
Date:
2025-11-29 16:55:03 UTC
Severity:
normal
#1071126#5
Date:
2024-05-14 18:31:16 UTC
From:
To:
* Package name    : battinfo
  Version         : 0.2.1
  Upstream Contact: Prasanna Venkadesh <prasmailme@gmail.com>
* URL             : https://gitlab.com/prashere/battinfo
* License         : GPL
  Programming Lang: Nim
  Description     : cli tool & nim-lang library to query battery info for GNU/Linux

 - This package can help users to query for their battery status & other
   details. This is not only a binary, but also a library for nim-lang,
   that also helps them import this library and query battery related
   information in their nim programs.

 - As a developer of battinfo, I pledge to maintain the debian package
   for it. It seems, there is no packaging team available yet for Nim lang.
   I am not looking for co-maintainers, it's not complex.
#1071126#10
Date:
2024-05-14 19:03:49 UTC
From:
To:
There does exist a nim team.

https://salsa.debian.org/nim-team

Best,
Nilesh
#1071126#15
Date:
2024-05-17 15:22:00 UTC
From:
To:
Oh! I couldn't find the team in this wiki https://wiki.debian.org/Teams

In that case, I would like the package to be managed under the team. I also notice that the package names for libraries follow nim-* pattern.

How about hybrids, when its both a CLI app & a library?

What are my next steps?
#1071126#20
Date:
2024-05-17 17:53:13 UTC
From:
To:
I suppose you need to name a package in a way that has more weight. Is it more
likely to be used by end users as a library or application? Name the source
package based on what makes more sense. As for battinfo, it makes more sense to
have an application name (battinfo instead of nim-battinfo).

You could contact the owners of nim team to grant you access to the salsa
namespace. If there's too much delay/you are in a hurry, you could use another
namespace for now.

Best,
Nilesh