I'd be more than happy to switch to another (shared) package, but both the "other" libvterm packages seem to have issues. `libvterm-bzr` conflicts with `libvterm` (an unrelated project) for whatever reason (see my comment to it), and `libvterm-git-neovim` that you suggest relies on using a neovim mirror of the bzr repository instead of using the upstream bzr repository directly. This, AFAICT, only introduces some lag between revisions for no good reason.
Agree about updating the description (well, the extra 'the' would be removed), though. I'd be happy to resolve the libvterm package situation as well.
I'm not sure what the issue is with pangoterm-libvterm-bzr currently? It seems to build the latest revision correctly--I guess I should update the verison string to "LATEST" or so since it's set by `pkgver`.
Search Criteria
Package Details: pangoterm-bzr r559-1
Package Actions
| Package Base: | pangoterm-bzr |
|---|---|
| Description: | GTK/Pango-based terminal emulator using the libvterm library |
| Upstream URL: | https://code.launchpad.net/pangoterm |
| Category: | x11 |
| Licenses: | |
| Provides: | |
| Submitter: | FireFly |
| Maintainer: | FireFly |
| Last Packager: | FireFly |
| Votes: | 3 |
| First Submitted: | 2012-11-28 17:11 |
| Last Updated: | 2014-07-21 13:54 |
Latest Comments
Comment by FireFly
Comment by dumblob
Due to conflicts between pangoterm-libvterm-bzr and libvterm-git-neovim, I've modified the following lines in PKGBUILD:
pkgdesc="GTK/Pango-based terminal emulator using the Leonerd's libvterm library"
depends=('libvterm-git-neovim' 'pango')
I've chosen the libvterm-git-neovim package, because it's actively maintained and will probably make it to community after some time (but under a different name).
Comment by aperez
@FireFly: Thanks for updating the PKGBUILDs. You don't really need to update later on for new versions, because the latest version from the Bazaar repositories will be picked up, and the “pkgver()” function will take care of updating (locally) the version to the latest in the repository. Which is just perfect for this kind of package like pangoterm/libvterm which do not have releases and the repository changes every now and then :)
Comment by FireFly
Oh oops, I forgot about the AUR package again... sorry.
Those PKGBUILDs look good, so I've updated the package to use those instead. I'll try to remember to check for updates to pangoterm/libvterm periodically.
Comment by aperez
I have been using a version of this PKGBUILD that uses always the latest revision from the repository. You can find it here:
https://github.com/aperezdc/pkgbuilds/blob/master/pangoterm-bzr/PKGBUILD
Also, for libvterm:
https://github.com/aperezdc/pkgbuilds/blob/master/pangoterm-libvterm-bzr/PKGBUILD
Notice how my versions of the PKGBUILDs put the repository URLs in the “source” array, and they have a “pkgver()” function to dynamically set the package version. Current versions of makepkg support those things directly.
Comment by JarrodH
Current rev of this should be 559 , but does move constantly.
When you do a lock / version of this, you need to do the one for pangoterm-libvterm-bzr as well, the two are tightly locked.
Comment by JarrodH
Getting build errors on this.
Comment by FireFly
Thanks, done.
Comment by lahwaacz
Please change the dependency to 'pangoterm-libvterm-bzr'.