Am 22.06.2015 um 15:32 schrieb Mark Weiman:

I was contacted by maintainer fwalch and he wants to submit a package that is named libvterm and is from this site ( http://www.leonerd.org.uk/code/libvterm/) and is concerned with how he should name it and how my package libvterm ( https://aur4.archlinux.org/packages/libvterm/) should be named.

Should my package be renamed and we both use something like "libvterm -something" or should mine remain as is and he name it "libvterm -something"?

Well, ideally one of the upstream maintainers renames his library because the name is already taken.

From what I found:

http://www.leonerd.org.uk/code/libvterm/ by Paul "LeoNerd" Evans is the "original" libvterm from 2007 [1] (Copyright 2008 in LICENSE). There is a Launchpad project [2] and also a GitHub mirror [2] as part of the NeoVim project. The last commit is from february this year. Also note that libvterm in Debian is the "LeoNerd" libvterm [4]. http://code.google.com/p/libvterm/ by Bryan Christ: The project was pushed to sourceforge [4] at 2010 [5] and it has Copyright 2009 in the source files. It looks kind of abandoned there. The new version is at Google Code. Interestingly, the SF repository was not migrated to Google Code but the last version from SF was checked in as the initial version at Google Code. The last change is from 2013 and Google Code is read-only so we can assume the project is dead. That means: libvterm should be http://www.leonerd.org.uk/code/libvterm/ on AUR/Arch and the Bryan Christ libterm should either have a suffix or the maintainer asked to rename the project altogether. This is not ideal, since the libvterm package already exists since 2009, has 14 votes and another package depends on this. However, the libvterm from this packages seems to be abandoned anyways. Note that vwm (having the libvterm dependency) is also by Bryan Christ and also abandoned. libvterm-vwm would make sense as a new name. greetings JonnyJD [1]: http://bazaar.launchpad.net/~leonerd/libvterm/trunk/changes/1 [2]: https://launchpad.net/libvterm [3]: https://github.com/neovim/libvterm [4]: https://packages.debian.org/source/experimental/libvterm [5]: http://sourceforge.net/projects/libvterm/ [6]: http://sourceforge.net/p/libvterm/code/commit_browser