Is there a way to check the current of version of gperf on my computer? I want to use gperf3.0.3 instead of gperf3.0.4 looks like the only way to check it right now is just to reinstall
as said by #Sean Bright gperf --version
Related
I am trying to install gnocchi-api, gnocchi-metricd and python-gnocchiclient with apt-get. I found that the postinst scripts in /var/lib/dpkg/info have some misconfigured ports due to which I cannot install the packages successfully. I wanted to ask if there is a way to change the post-installation scripts nad then re-install the package.
Thanks.
Ideally this kind of problems would be solved by filing a bug report (possibly with a patch) and letting the maintainer upload a fixed version that you can upgrade to.
If you need an immediate local workaround though, you could do the following:
Either apt download <package> or dpkg-repack <package> if for example this is a local package only, or the archive does not contain the version you are interested in f.ex.
dpkg-deb -R <package_version_arch>.deb bin-dir
sensible-editor bin-dir/DEBIAN/postinst
sensible-editor bin-dir/DEBIAN/control ideally to bump the version to mark this as a local modification, say by appending +local1 or similar.
dpkg-deb -b bin-dir .
dpkg -i <package_local-version_arch>.deb
I want use oh-my-zsh jhipster plugin. I followed Jhipster guidelines using
http://www.jhipster.tech/oh-my-zsh/
After setting up everything, whenever i try to use command jh, it doesn't work. I get response
zsh: command not found
I'm not familiar with shell scripting language. Please help me.
Yes, you need to:
install zsh
install oh-my-zsh
configure your default shell to use zsh -> it is important
install jhipster-oh-my-zsh-plugin
Here the commands we do for our jhipster-devbox (on Ubuntu):
https://github.com/jhipster/jhipster-devbox/blob/master/scripts/setup.sh#L100-L112
Did you installed zsh?
I am not familiar with MAC, but it should be something like:
brew install zsh zsh-completions
here some more in-deep instructions:
http://sourabhbajaj.com/mac-setup/iTerm/zsh.html
I want to start developing of my first test addon. I have a problem on the basis of mr.bob. Any described ways have leaded to one result. my documentation
log image
Check
mrbob --help
do the same answer.
After I came to the conclusion the problem is in pre-installed Python2.7 with no worked mr.bobe and bobtemplates. I do not know how to make a working set.
Looking at your traceback I guess mr.bob is not fully supporting Windows.
The readline module on Windows is not available. There's some alternatives like pyreadline.
Seems it's a know issue: see https://github.com/domenkozar/mr.bob/issues/49
Don't know about mr.bob, but you could alternatively try adi.devgen (disclaimer: one of my add-ons). Install it with pip:
pip install adi.devgen
And then do:
devgen addOn yournamespace.youraddonname
I haven't been able to find the help I need on (on dummie level) for installing a new dictionary (danish) in emacs. To be honest I somewhat confused about ispell vs aspell. When typing "M-x ispell-buffer" a spelling control starts using english as default. I can change directory typing "M-x-ispell-change-dictionary" it suggest "dansk" but I get an error saying that the file /.../aspell/dict/danish" can not be opened for reading. I can deduct that the dictionary is not installed - but I cannot seem to finde a guide (step by step) on how to do this.
And then I have a bonus question. I have managed to install flyspell (or is that actually 'installing' as I have just addet the .el file to my emacs load path and loaded in my .emacs file?). This seem to work (wauw), and as I understand it flyspell is using the same dictionaries as ispell/aspell hence solving my probleme above would enable me to use flyspell in danish?
Any help is appreciated.
/Kira
If you are on Ubuntu or Debian system you can install the Danish aspell package from the commandline with
sudo apt-get install aspell-da
The readline library allows the CLI for sqlite to accept arrow keys to recall previously typed commands. I can build without this and sqlite works, it's just a hassle not having this nice capability. I've installed readline-devel from yum and /usr/lib64/libreadline.so.5 is present as well as it's header files. When I run ./configure to build sqlite, I see these lines:
checking for library containing readline... no
checking for readline... no
The library path is set to the correct path:
LD_LIBRARY_PATH="/usr/lib64:/usr/local/lib:/lib:/usr/lib"
By default, ./configure does try to include readline support so there are no special "--with-XXXX" options needed.
Anyone every seen this problem? I need to use this newer version to get latest foreign key support. It's hassle running on CentOS as is bundles pretty old versions of apps but we don't have a choice right now and I cannot find an updated RPM with newer version of sqlite.
=== UPDATE ===
Ok, I found a solution but I don't completely like it...
First, I tried with this option:
./configure CPPFLAGS="-I/usr/include/ -DHAVE_READLINE"
That causes the readline functionality to get compiled into shell.c which is what is needed for starters. But, the linking fails because it cannot find libreadline. The only 'kludgy' way I could figure out to get it to link was to manually edit the Makefile after running the above ./configure command. I changed this line:
LIBS = -ldl -lpthread
to this:
LIBS = -ldl -lpthread -lreadline -ltermcap
Then I ran "make clean all" and "make install" and the readline functionality works in the CLI.
I tried every way I could think of to pass in the extra libraries including exporting using LIBS, exporting using READLINE_LIBS, exporting using LDFLAGS, nothing would work. If you set LIBS to anything, like "export LIBS="-lreadline", it causes configure to fail. The --help on configure about using LIBS seems to contradict what happens when you actually set it to any value.
Anyway, this works so I can live with it - but I don't particularly like it! :(
==== THE RIGHT SOLUTION ====
Well, wouldn't you know it. Spend hours trying to figure it out, then stumble onto the right tip on Google. Just needed to install ncurses-devel first. So, to summarize all that is needed to built it 'unkludgily':
yum install ncurses ncurses-devel
yum install readline readline-devel
yum install libtermcap libtermcap-devel
./configure
make
make install
No special command line options or exports or Makefile edits needed! Readline support is automatically built in by default now.