rpm | 易学教程

CentOS7离线编译安装PostgreSQL11

阅读更多关于 CentOS7离线编译安装PostgreSQL11

这是博客是转载的，原博客步骤很详细，写得非常好。这是具体教程。本人只是补充几个具体操作细节。一、准备编译环境建议采取原博中的方式一。因为极有可能服务器中的版本会低于镜像站里的版本，网上很难找到。直接使用服务器装机镜像是最省事的。挂载镜像文件到服务器将服务器镜像（.iso文件）上传到服务器后挂载到服务器后就可以直接使用里面的rpm包。将服务器镜像挂载到 media目录下，命令如下， mount /opt/CentOS-7-x86_64-DVD-1810.iso /media/ -o loop 查看挂载后的rpm包： ll /media/Packages -ls | more 四、编译安装一般服务器会缺少3个，除了博客中所述的2以外，会缺少zlib包，安装如下： rpm -ivh ncurses-devel-5.9-14.20130511.el7_4.x86_64.rpm rpm -ivh readline-devel-6.2-10.el7.x86_64.rpm rpm -ivh zlib-devel-1.2.7-18.el7.x86_64.rpm 最后在验证非本地客户端连接数据库时，除了博客中所述的Navicat Premium，还可以使用PostgreSQL自己的管理客户端pgAdmin3或者pgAdmin4。来源： CSDN 作者： ceshell 链接：

Centos7下安装MySQL5.7.28(rpm安装)

阅读更多关于 Centos7下安装MySQL5.7.28(rpm安装)

我的是centos7.6，MySQL的版本是5.7.28. mysql-5.7.28-1.el7.x86_64.rpm-bundle.tar 。里面是一些mysql的rpm安装集合包。 1. 安装：我们已经将从官网上下载的rpm安装集合包到本地window上，将这些安装集合包上传到我们的centos系统上，上传到/opt/software目录下。 1.1: 建立一个目录，用于存储tar文件解压后的文件。 [root@one opt] # pwd / opt [root@one opt] # mdkir mysql [root@one opt] # ll 总用量 4 drwxr - xr - x . 5 root root 68 10月 31 19:34 module drwxr - xr - x . 2 root root 4096 11月 1 10:37 mysql drwxr - xr - x . 2 root root 181 11月 1 10:37 software 1.2: 在/opt/soteware下解压.tar的安装包 [root@one software] # tar -xf mysql-5.7.28-1.el7.x86_64.rpm-bundle.tar -C ../mysql/ 1.3：可以看到/opt/mysql目录下有很多.rpm包 1.4.

ELK日志监控平台安装部署简介--Elasticsearch安装部署

阅读更多关于 ELK日志监控平台安装部署简介--Elasticsearch安装部署

最近由于工作需要，需要搭建一个ELK日志监控平台，本次采用Filebeat（采集数据）+Elasticsearch（建立索引）+Kibana（展示）架构，实现日志搜索展示功能。一、安装环境描述：　　1、JDK1.8以上版本；　　2、CentOS release 6.10 (Final) x86_64 二、Elasticsearch安装部署　　2.1 官方网站　　　　Elasticsearch： https://www.elastic.co/downloads/elasticsearch 　　　　Kibana： https://www.elastic.co/downloads/kibana 　　　　Filebeat： https://www.elastic.co/downloads/beats/filebeat 　　2.2 安装方式　　　　这里采用RPM安装方式，要在root权限下安装。　　　　为什么采用RPM安装方式？　　　　因为采用这种方式安装，直接可将软件安装成服务，可采用service命令启动; 　　　　2.2.1 安装　　　　这里我采用的是6.3.2版本；　　　　依次执行以下命令：　　　　　　wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-6.3.2.rpm

RPM spec files in version control system

阅读更多关于 RPM spec files in version control system

问题 I faced with task of building RPM packets from sources of c++ (but it may be any other language) project controlled with Git. And my question is where should I store ".spec" files for this task? Should it be stored independently of project main sources or be included in them? This task is complicated by the condition that I'm participating in different projects and use different version control systems: SVN, Git, Mercurial. So I'm trying to find most common and convenient solution without

How to create RPM subpackages using the same paths for different envs?

阅读更多关于 How to create RPM subpackages using the same paths for different envs?

问题 I would like to use a rpm to build subpackages for different environments (live,testing,developer) but for the same files, so having a package called name-config-live, one called name-config-testing and one called name-config-developer and in them to have the same paths but each with the configs corresponding to the environment it's named after. as an example let's say on all environments I have a file called /etc/name.conf and on testing I want it to contain "1", on development "2" and on

distutils setup.py and %post %postun

阅读更多关于 distutils setup.py and %post %postun

问题 I am newbie. I am buidling rpm package for my own app and decided to use distutils to do achieve it. I managed to create some substitue of %post by using advice from this website, which i really am thankfull for, but i am having problems with %postun. Let me describe what i have done. In setup.py i run command that creates symbolic link which is needed to run application. It works good but problem is when i want to remove rpm, link stays there. So i figured that i should use %postun in spec

excluding file types when packaging an rpm

阅读更多关于 excluding file types when packaging an rpm

问题 In my spec file for packaging a python rpm, I want to remove certain filetypes in certain directories: e.g., I want to exclude source *.py files in these directories: lib/*.py comm/*.py I think I should do this in the %file section of my spec. Any suggestions? 回答1: At one point in the distant past, you did that by just not including the files you didn't want in the %file section, and so they would not be packaged. That might have turned out to be too error prone, and so some RPM

File listed twice in rpm spec file

阅读更多关于 File listed twice in rpm spec file

问题 The files section of my spec-file looks like this: %files %{prefix}/htdocs/ %config %{prefix}/htdocs/share/settings/config.inc.php Now, since the config file is already included in the %{prefix}/htdocs/ line I get the warning 'File listed twice'. One way around would be, to list every single file within %{prefix}/htdocs/ , except the config file. But my question is: Is there a better way around this issue, than listing all files? 回答1: Unfortunately not. RPM is quite oldschool software, but

File listed twice in rpm spec file

阅读更多关于 File listed twice in rpm spec file

bdist_rpm from Ubuntu to CentOs

阅读更多关于 bdist_rpm from Ubuntu to CentOs

问题 We develop on Ubuntu/Macs and deploy RPMs to CentOS (this is the settings, can't be changed much). The problem is that when installing from the rpm, the packages go to /usr/local/lib/python2.7/dist-packages (which is the right location for Ubuntu). However the default python path in CentOS is looking at /usr/local/lib/python2.7/site-packages . Is there a way to tell bdist_rpm where to install the files to? 回答1: You can use a setup.cfg file to override the Python lib install path: setup.cfg :