How to invoke RPM as service - rpmbuild

How to start or invoke a service from RPM after installing it.
As I have rpm package and installed it using rpm -ivh pidgin-2.7.9-5.el6.2.i686.rpm, now I want to invoke the rpm automatically

you cannot "invoke an rpm"; an rpm just installs certain files on your system. That does not even mean that any of those files is executable. The command to launch the application will also always be different (systemctl, init.d, just launch the binary, ...).

Related

ACE/TAO build an rpm after sucessful make

ACE and TAO is used for our deployment and they will be required to be packaged as RPM from now on (for SUSE platform if it matters).
While I know there are RPM files available we have some specific "$ACE_ROOT/include/makeinclude/platform_macros.GNU" file that we use and we would like to have the RPM build out of the binaries resulted from our own build.
Can we create an RPM after following the steps from ACE-INSTALL.html, based on that build output?
See ACE_wrappers/rpmbuild for the spec file that is used for all RPMs on OpenSuSE Build service. Couldn't you extend that script with the options you need and contribute that back into the main github repo?

How do I upgrade MinTTY in Git for Windows

I appreciate that this is borderline off-topic, but it does "directly involve programming or programming tools" so I figure it's just about OK...
I've just installed a newly downloaded version of Git for Windows, and noticed that in the Options dialog, the title bar says "mintty 2.8.5 is available". According to the About dialog, I currently have version 2.8.4.
I assume it's telling me that there's a new version because I am able to upgrade it myself, but I can't find any information about how to do so. I've downloaded the zip file from mintty.github.io, but don't really want to have to build it manually if I can avoid it.
Is there some way to do this, or is the easiest option just to wait for an updated build of Git For Windows that includes the new version of MinTTY?
mintty is a terminal emulator program available for Cygwin and msys2 environment. In both environment, mintty can be compiled as 32bit and 64bit. Hence it will be easy to deploy if users/package maintainer compile themselves with their own toolchain. Here are the two mainstream toolchain associated with mintty.
Cygwin: You can search the full package namecygwin package search. Cygwin maintains multiple mirror URLs to download a package. Here is one of the mirror:
32bit: https://mirrors.kernel.org/sourceware/cygwin/x86/release/mintty/
64bit: https://mirrors.kernel.org/sourceware/cygwin/x86_64/release/mintty/
msys2: msys2 also maintains mirror URLs to download. You can browse whole packages list in http://repo.msys2.org/. Open that URL in a browser. As mintty need msys2 dynamic library, it can be found in msys2 directory. Search mintty in these webpages:
32bit: http://repo.msys2.org/msys/i686/
64bit: http://repo.msys2.org/msys/x86_64/
To use it in Git-For-Windows, download the mintty tarball file from msys2 links according to your installed one 32bit or 64bit. You can find mintty.exe in that .tar.xz file's usr/bin folder. Extract and place that executable in Git-For-Windows installation folder e.g. C:\Program Files\Git\usr\bin.
Note: Mintty need a dynamic library (e.g. cygwin1.dll or msys-2.0.dll) and a shell (e.g. bash.exe, dash.exe etc.) or a command line program to run. And it should be placed in /usr/bin or /bin folder as per your specific environment. For Cygwin specifically, you also need cygwin-console-helper.exe to hide the console window (conhost.exe process). In msys2 environment, mintty version may be lower than the Cygwin one.
I was having a similar issue with Git Bash saying "mintty 3.5.2 available". I simply used the following command in Git Bash.
git update-git-for-windows
It re-ran the installer and updated both my Git for Windows and mintty versions to the latest ones. The command is only valid from Git for Windows v2.16.1(2) though.

Install built meteor package

I built the meteor package as follow:
meteor build /tmp
It built the jar.gz file.
Now How do install this on different server?
Thanks
upload the tar file using ftp or scp on the terminal.
untar it on the server
cd bundle/programs/server
npm install
node bundle/main.js
Additional info:
use pm2 on the server so you can manage the node process seamlessly.
OR
use forever to run your app even if you quit the terminal.

How to specify RPM_BUILD_ROOT for sbt-native-package

I have a Play project that I would like to deploy via RPM. I'm trying to use SBT to build the RPM, on CentOS, using the sbt-native-packager RPM plugin.
At the end I gt the rpm package.
But it stored in directory under %appname%/target/rpm
How can I use my own path for rpm buildroot tree?
Say, for example /home/build/buildroot
Sbt-native-packager version in use 0.8.0.
The simple (rpm config centric) answer is to configure %_topdir in ~/.rpmmacros before invoking rpmbuild. SBT may be adding additional complexities.

Have configure.ac But Not autoconf. Can I Generate Configure Without It?

I'm trying to build curl...specifically libcurl...on my Android device; I've built OpenSSL and have cloned the repo. Unfortunately the curl sources use buildconf, which requires autoconf, and I don't have autoconf installed.
Is there an alternate way to generate the configure script and/or the Makefile from the included configure.ac and Makefile.in?
The source tarballs provided by the curl project include generated configure scripts, no need for autoconf then! You can get release versions or daily snapshots from curl.haxx.se.
The configure script is generally generated with the ./buildconf script in the curl source code root directory and it requires autoconf, automake and libtool to be installed.

Resources