Skip Menu |

This queue is for tickets about the Term-VTerm CPAN distribution.

Report information
The Basics
Id: 105364
Status: rejected
Priority: 0/
Queue: Term-VTerm

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.02
Fixed in: (no value)



Subject: vterm detection does not work on FreeBSD
On FreeBSD 10.1 the vterm detection does not seem to work: $ pkg-config vterm --atleast_version 0 pkgconf: unknown option -- atleast_version vterm is installed; it just looks like pkg-config does not support the --atleast_version option: $ pkg-config vterm ; echo $? 0 $ pkg-config --version vterm 0.28
On Fri Jun 19 01:23:12 2015, SREZIC wrote: Show quoted text
> $ pkg-config --version vterm > 0.28
This is a silly behaviour of pkg-config; what that's done is output the version of pkg-config itself (and ignored the trailing argument) What you want to do is $ pkg-config --modversion vterm And see if it outputs 0.0 (which is correct), or @VERSION@ (which would mean it was installed wrongly and needs reinstalling). -- Paul Evans
On 2015-06-19 04:52:21, PEVANS wrote: Show quoted text
> On Fri Jun 19 01:23:12 2015, SREZIC wrote:
> > $ pkg-config --version vterm > > 0.28
> > This is a silly behaviour of pkg-config; what that's done is output > the version of pkg-config itself (and ignored the trailing argument) > > What you want to do is > > $ pkg-config --modversion vterm > > And see if it outputs 0.0 (which is correct), or @VERSION@ (which > would mean it was installed wrongly and needs reinstalling).
Output is @VERSION@ here. vterm is installed via a freebsd package (libvterm-git20150527). Does this really mean that the package is broken?
On Sat Jun 20 04:29:36 2015, SREZIC wrote: Show quoted text
> Output is @VERSION@ here. vterm is installed via a freebsd package > (libvterm-git20150527). Does this really mean that the package is > broken?
That means it was built directly from a source checkout ((curious that it says 'git' there because I version it with bzr)) rather than from a packed source tarball, from before the revision where that made a difference. Best would be to update upstream to fix it. Once you get "0.0" instead of "@VERSION@" there, then things should be fine. -- Paul Evans
On 2015-06-20 04:59:34, PEVANS wrote: Show quoted text
> On Sat Jun 20 04:29:36 2015, SREZIC wrote:
> > Output is @VERSION@ here. vterm is installed via a freebsd package > > (libvterm-git20150527). Does this really mean that the package is > > broken?
> > That means it was built directly from a source checkout ((curious that > it says 'git' there because I version it with bzr))
The freebsd port fetches the source code from https://github.com/neovim/libvterm I guess the mirror exists because freebsd's port system only handles git (or github) and not bzr... Show quoted text
> rather than from a > packed source tarball, from before the revision where that made a > difference. > > Best would be to update upstream to fix it. Once you get "0.0" instead > of "@VERSION@" there, then things should be fine.
On 2015-06-20 04:59:34, PEVANS wrote: Show quoted text
> On Sat Jun 20 04:29:36 2015, SREZIC wrote:
> > Output is @VERSION@ here. vterm is installed via a freebsd package > > (libvterm-git20150527). Does this really mean that the package is > > broken?
> > That means it was built directly from a source checkout ((curious that > it says 'git' there because I version it with bzr)) rather than from a > packed source tarball, from before the revision where that made a > difference. > > Best would be to update upstream to fix it. Once you get "0.0" instead > of "@VERSION@" there, then things should be fine.
-> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200996
On Sat Jun 20 14:50:02 2015, SREZIC wrote: Show quoted text
> The freebsd port fetches the source code from > https://github.com/neovim/libvterm > I guess the mirror exists because freebsd's port system only handles > git (or github) and not bzr...
Actually I believe that mirror exists because neovim applied some local modifications to the library, before I could get around to properly upstreaming them. That mirror shouldn't be considered canonical. -- Paul Evans
Closing as a variant of "user error" -- Paul Evans