Hi! I'd like to point out that the package `libvterm` on AUR provides an unrelated project, so I think the package name `libvterm-bzr` (as well as conflicting with/providing `libvterm`) is a bad idea.
This is the reason I named my similar package `pangoterm-libvterm-bzr` (at the time I don't think there were many other projects using it). It's not a terribly good name either, but at any rate it seems pointless to have two equivalent packages with different names.
Search Criteria
Package Details: pangoterm-libvterm-bzr r617-1
Package Actions
| Package Base: | pangoterm-libvterm-bzr |
|---|---|
| Description: | An abstract library implementation of a VT220/xterm/ECMA-48 terminal emulator, not to be confused with the other package called 'libvterm'. |
| Upstream URL: | https://launchpad.net/libvterm |
| Category: | lib |
| Licenses: | |
| Provides: | |
| Submitter: | FireFly |
| Maintainer: | FireFly |
| Last Packager: | FireFly |
| Votes: | 4 |
| First Submitted: | 2012-11-28 17:07 |
| Last Updated: | 2014-07-21 13:56 |
Latest Comments
Comment by FireFly
Comment by JarrodH
Current rev of this is 617. Keeping this and pangoterm in lock sync should be good, or using revno / HEAD also works :D
Thanks for the prompt reply.
Comment by FireFly
Thanks. I'll take a look on this (and pangoterm-bzr) next week and update the PKGBUILDs.
Comment by JarrodH
This bzr needs to change to Leo's bzr server at:
http://bazaar.leonerd.org.uk/c/libvterm/
Homepage for project is now:
http://www.leonerd.org.uk/code/libvterm/