Request: release the package in apt

[osbm]

What the title says. Is there any plans to bring tlrc into apt? So that ubuntu/debian users can install the software very easily something like this:

sudo apt install tlrc

Just to provide a little more smooth user experience 😅

[acuteenvy]

I have absolutely no experience with creating deb packages, and I am not a maintainer in any of these distributions. It would be great if someone packaged tlrc for Debian and Ubuntu, but unfortunately all I can do is wait for a maintainer that is willing to put it in the official repositories.

[kbdharun]

Hi, thanks for expressing your interest in seeing tlrc in native distribution repositories, I would suggest dropping a mail requesting the same to debian-rust@lists.debian.org (The Debian Rust mailing list https://lists.debian.org/debian-rust/) or contacting them via other channels listed at https://wiki.debian.org/Teams/RustPackaging.

Note: Most common/normal packages added in Debian repos will directly be available in Ubuntu repos too.

[osbm]

Thanks for the replies, I still have some questions. Because i dont have much experience in producing/publishing linux packages. Only using them :)

How do you upload your package to all these distro package managers?
Do you just make a release by hand after the build github action compiles a binary or something? Or do they initiate this automatically by the github release webhook?

I will try to send a request to the Debian-Rust mailing list. Do they handle making the deb file or do we still need to produce a gpg signed deb file to hand over to them?

[acuteenvy]

How do you upload your package to all these distro package managers?

It depends on the package manager. That being said, you can never just upload a binary package to the official repositories. Maintainers of that repository have to create the package themselves. Some repositories allow users to contribute packages, but that is not the case for Debian, as far as I know.

Do you just make a release by hand after the build github action compiles a binary or something?

The packages that I maintain are updated by me after a release. For other repositories, I just wait for the maintainers to update.

Do they handle making the deb file or do we still need to produce a gpg signed deb file to hand over to them?

They handle that themselves.

[kbdharun]

Adding to acuteenvy's points above, basically Debian and other distribution repositories directly rebuild the project from the release source code archives (i.e. tar.gz file) of the upstream package (us). So having a DEB here in our release assets isn't that useful (but it would allow manual install but then you won't get updates).

How do you upload your package to all these distro package managers?

We don't, we package our clients directly in distro-agnostic sources like Homebrew, etc and the community re-packages them for their distribution of choice.

I will try to send a request to the Debian-Rust mailing list. Do they handle making the deb file or do we still need to produce a gpg signed deb file to hand over to them?

They will handle the DEB packaging completely (along with a bug tracker for tracking packaging issues).

[HernandoR]

Since i'm installing from prebuild binary, how should i install the completions?

[acuteenvy]

Since i'm installing from prebuild binary, how should i install the completions?

Assuming you mean the tarball in GitHub releases - inside the archive is a directory called completions. There are files for bash, zsh and fish. You have to put them in the appropriate directory for your shell:

• bash: $XDG_DATA_HOME/bash-completion/completions (documented here)
• fish: $XDG_CONFIG_HOME/fish/completions (documented here)
• I couldn't find anything standard for zsh, and I don't use it myself, but there probably is a way to do this.

Keep in mind that if you just copy the completion files from the release archive they won't ever be updated, unless you do so manually. But this is the only way to install completions if they aren't packaged for your distribution.

[JoeJoeTV]

I just saw this conversation and though that maybe this project could be used to provide a way to build a deb package easily: https://github.com/kornelski/cargo-deb

EDIT: I added metadata to use this with cargo-deb in this pull request: #139

[acuteenvy]

deb packages built with cargo-deb are now on GitHub releases.
https://github.com/tldr-pages/tlrc/releases/tag/v1.12.0

[vaskark]

With the new deb packages ... the completions don't work for zsh in either deb.

[JoeJoeTV]

With the new deb packages ... the completions don't work for zsh in either deb.

I based the paths for the completions on the PKGBUILD of the AUR package: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=tlrc-git

I guess I should have checked for distro differences, as debian based distros seem to use /usr/share/zsh/vendor-completions/, while others use /usr/share/zsh/site-functions/.
I will make a PR fixing this as soon as i'm home.

[vaskark]

I guess I should have checked for distro differences, as debian based distros seem to use /usr/share/zsh/vendor-completions/, while others use /usr/share/zsh/site-functions/. I will make a PR fixing this as soon as i'm home.

That's what's weird. Ubuntu does have zsh completions in /usr/share/zsh/site-functions as well and they do work there. I've always wondered why there isn't just 1 location for them.

Ideally:

/usr/share/$SHELL/completions

[JoeJoeTV]

I guess I should have checked for distro differences, as debian based distros seem to use /usr/share/zsh/vendor-completions/, while others use /usr/share/zsh/site-functions/. I will make a PR fixing this as soon as i'm home.

That's what's weird. Ubuntu does have zsh completions in /usr/share/zsh/site-functions as well and they do work there. I've always wondered why there isn't just 1 location for them.

Ideally:

/usr/share/$SHELL/completions

Do bash completions work for you?

[vaskark]

@JoeJoeTV Sorry, should have stated before that both bash and fish work fine.