@kali-team, please could this be packaged up.
@author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

morning!

Tool author here; a friend of mine let me know this was here. I'll see if I can get this working today.

I took a look at the link from @g0tmi1k, it doesn't look like the normal debian build process. It seems as though it's mostly an install script and some of the debian build files?

It doesn't appear that cargo/rustc is included in kali. I currently distribute musl-built static binaries via github actions. Are there any considerations/standards for packaging a rust project?

@epi I have no experience in rust project packaging but I think this link can help you to start:
https://salsa.debian.org/rust-team/debcargo-conf/blob/master/README.rst

It's the documentation of the rust-team in Debian (there is some information that is only relevant for Debian like ITPs).

@sbrun ill take a look at that; I haven't been successful yet without it, lol

@sbrun I've got this all working. How do I handle the final remote repo? Following through the documentation, i have this in my debian/control

Homepage: https://github.com/epi052/feroxbuster
Vcs-Browser: https://gitlab.com/kalilinux/packages/feroxbuster 
Vcs-Git: https://gitlab.com/kalilinux/packages/feroxbuster.git

Should I create a 'packaging' repo on gitlab instead, or do ya'll create one that i can push/PR to?

@epi You don't need to create a 'packaging' repo on gitlab.
You can create a branch on your github repo including the debian directory.

I will create the repo on gitlab.com/kalilinux and will import your pacakging work.

@sbrun i pushed the three branches and tags to https://github.com/epi052/feroxbuster.

What's the normal way of handling those branches going forward? I assume I can merge kali/master, putting debian/ into my main branch. What about pristine-tar and upstream?

@epi thanks for the packaging. I will import it into kali as soon as possible.

You don't need to keep pristine-tar and upstream in your repo.
They are required only in kali repo. They wil be updated by importing new upstream tarball.

For the kali/master branch, you can do what you want: you can keep it or/and merge it into your main branch or/and remove it.

new version 2.2.1-0kali1 is in kali-rolling