Arch Linux User Repository

While the original Termite maintainers recommend Alacritty now and stopped development, there are still reasons to use Termite—for example if your box does not have OpenGL or Rust does not work for your architecture.

This fork of Termite is actively maintained: it is kept updated with the latest VTE versions, fixes and new features get merged, and whenever enough changes are gathered in the main branch new releases are produced as well :)

@thiagowfx yes.

I checked his package, and the upgrade to meson to compile termite and vte together is quite nice.

We maybe need to decide if this package (termite) should follow the upstream repo or could use a fork.

@barbuk, would you be willing to merge this package with https://aur.archlinux.org/packages/termite-aperezdc/?

In other words, would you be willing to add the current maintainer of the other package as co-maintainer of this one?

@FabioLolix, @thiagowfx: I will be fine collaborating and merging packages if that's the decision on this topic. I think that my fork should be what get built by the termite package, because I have been merging fixes in Termite itself and not only keeping up with the latest VTE releases :)

I uploaded termite-aperezdc as soon as I forked Termite to continue development while the original termite package was still in the official Arch repositories, which is the only reason why I did not use the termite name in the AUR.

While I do not plan to make any big new features right now, my plan is to continue doing light maintenance, fixes, and reviewing any patches that come my way. I even tried contacting the original Termite author a few times to see if I could take over maintenance without forking, but I never got a reply back ¯_(ツ)_/¯

For the moment I would left the things as is, aperezdc have been working on termite for a longer time then barbuk, and barbuk haven't replied if he want to collaborate with aperezdc.

@FabioLolix In this case it would be nice to merge this package with the other termite.

Something similar recently happened for https://aur.archlinux.org/packages/i3blocks-contrib-git/: there used to be two packages, and they got merged into a single one, in that case the maintainer of the canonical package was inactive so the other maintainer took it over, with the blessing of a TU.

In this case it seems that both maintainers (for termite and termite-aperezdc) are active, so the ideal scenario would be that maintainer of termite adds aperez as co-maintainer, and then this package be deleted.

@thiagowfx Termite was dropped from the official repository because it has been 'archived' upstream as you can read here: https://github.com/thestinger/termite/

I don't know why it has been uploaded to the AUR since termite-aperezdc was already here and updated meanwhile.

For comparison when glimpse was archived on github the AUR pkgbuilds glimpse/glimpse-git where deleted in like 2 days.

Hi, could you elaborate why this package would be useful to other AUR users (compared to, example, https://aur.archlinux.org/packages/termite/)?

AUR Guidelines say:

Make sure the package you want to upload is useful. Will anyone else want to use this package? Is it extremely specialized? If more than a few people would find this package useful, it is appropriate for submission.

Given this package is literally named after your own username, it seems to contain customizations for you only. Is this correct? If so, it's more appropriate to host it elsewhere.

Edit: Just to make it clear, I was about to file a deletion request for it, but out of courtesy given that you have recently updated this package I am asking it in the comments first.

It's also useful when OpenGL is temporarily broken, e.g. the time between updating the kernel and rebooting

@FredBezies, alacritty requires GLSL 3.30, and that's why it's useless on an older machine. I know that you can set LIBGL_ALWAYS_SOFTWARE, but then alacritty loses all points as a "GPU accelerated terminal". It uses 10% of CPU resources just for running htop on an old ThinkPad! IMHO termite is still relevant, it has all necessary features, and alacritty is not a valid replacement for termite for all use cases.

Hello BarbUk, I have seen you have forked vte-ng for fixing problems (and termite on github), there is also this https://aur.archlinux.org/packages/termite-aperezdc, there could be room for collaboration?

If you plan to develop on your own termite, re-uploading as termite-barbuk should be done