centos | Odoo Connects Everything

centos install flash player projector content debugger

众所周知，Adobe Flash Player 11.2将是支持Linux平台的最后一个版本，不过Google Chrome自带的Flash Player Plugin版本不受这个限制，但Adobe将继续为Flash Player 11.2 for Linux提供安全更新

Flash基础环境除了依附浏览器的Plugin版本外，还有一种Projector版本，即独立播放器程序。虽然插件版已经支持64位系统了，但播放器版本官方始终只提供32位程序包下载

下载地址（含debug版本）
http://www.adobe.com/support/flashplayer/debug_downloads.html

Linux Help（2011年11月版本）
https://helpx.adobe.com/flash-player/release-note/readme-flash-player-linux.html

文档目前只有FP9和FP10的依赖库列表说明，最新也是最后版本的FP11详情很遗憾还未更新
为了避免安装不必要的32位旧依赖库，可以通过启动时缺少库提示来按需安装，如：

[root@x1c flash]# ./flashplayer
./flashplayer: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory

[root@x1c flash]# yum whatprovides libgtk-x11-2.0.so.0
gtk2-2.24.28-8.el7.i686 : The GIMP ToolKit (GTK+), a library for creating GUIs for X
源    ：base
匹配来源：
提供    ：libgtk-x11-2.0.so.0

[root@x1c flash]# yum install gtk2.i686 -y

[root@x1c flash]# ./flashplayer

./flashplayer: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory

[root@x1c flash]# yum whatprovides libgtk-x11-2.0.so.0

gtk2-2.24.28-8.el7.i686 : The GIMP ToolKit (GTK+), a library for creating GUIs for X

源：base

匹配来源：

提供：libgtk-x11-2.0.so.0

[root@x1c flash]# yum install gtk2.i686 -y

由于每个人的基础环境异同需要补上的32位库也不尽相同，记得上回安装Android SDK时大规模安装过一次，可能有些依赖相同的都省了，本次最终更新列表如下：

glib2.i686
libX11.i686
libXext.i686
libXt.i686
libXcursor.i686
nss.i686(libssl3.so)
gtk2.i686(libgtk-x11-2.0.so.0)

glib2.i686

libX11.i686

libXext.i686

libXt.i686

libXcursor.i686

nss.i686(libssl3.so)

gtk2.i686(libgtk-x11-2.0.so.0)

yum完上述i686基础依赖库，剩下的就是运行时报错的解决了，相关过程如下

GTK默认加载adwaita主题警告：

(flashplayer:13285): Gtk-WARNING **: 无法在模块路径中找到主题引擎：“adwaita”

yum install adwaita-gtk2-theme.i686 -y

(flashplayer:13285): Gtk-WARNING **: 无法在模块路径中找到主题引擎：“adwaita”

yum install adwaita-gtk2-theme.i686 -y

GTK默认加载PackageKit模块提示：

Gtk-Message: Failed to load module "pk-gtk-module"

yum install PackageKit-gtk3-module.i686 -y

Gtk-Message: Failed to load module "pk-gtk-module"

yum install PackageKit-gtk3-module.i686 -y

GTK默认加载libcanberra模块提示：

Gtk-Message: Failed to load module "canberra-gtk-module"

yum install libcanberra-gtk2.i686 -y

Gtk-Message: Failed to load module "canberra-gtk-module"

yum install libcanberra-gtk2.i686 -y

运行时闪退：

(flashplayer:15762): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
(flashplayer:15762): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

yum install libcurl.i686 -y

(flashplayer:15762): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer

(flashplayer:15762): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

yum install libcurl.i686 -y

运行时无声：

ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so

yum install alsa-plugins-pulseaudio.i686 -y

ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so

yum install alsa-plugins-pulseaudio.i686 -y

折腾完毕之后运行flashplayer或flashplayerdebugger一切顺利

centos odoo decoder jpeg not available

云服务器上传jpg图片提示IOError错误

  File "/usr/lib64/python2.7/site-packages/PIL/ImageFile.py", line 200, in load
    d = Image._getdecoder(self.mode, d, a, self.decoderconfig)
  File "/usr/lib64/python2.7/site-packages/PIL/Image.py", line 417, in _getdecoder
    raise IOError("decoder %s not available" % decoder_name)
IOError: decoder jpeg not available

File "/usr/lib64/python2.7/site-packages/PIL/ImageFile.py", line 200, in load

d = Image._getdecoder(self.mode, d, a, self.decoderconfig)

File "/usr/lib64/python2.7/site-packages/PIL/Image.py", line 417, in _getdecoder

raise IOError("decoder %s not available" % decoder_name)

IOError: decoder jpeg not available

初步判断是python pil库依赖的底层jpeg lib问题
但是本机正常无法重现，于是检查环境

[srj@x1c ~]$ yum list installed|grep jpeg
libjpeg-turbo.x86_64               1.2.90-5.el7                        @anaconda
libjpeg-turbo-devel.x86_64         1.2.90-5.el7                        @anaconda
openjpeg-libs.x86_64               1.5.1-10.el7                        @anaconda

[srj@x1c ~]$ yum list installed|grep jpeg

libjpeg-turbo.x86_64 1.2.90-5.el7 @anaconda

libjpeg-turbo-devel.x86_64 1.2.90-5.el7 @anaconda

openjpeg-libs.x86_64 1.5.1-10.el7 @anaconda

对比了下发现服务器环境没有libjpeg-turbo-devel.x86_64立马补装一个，重启odoo服务错误依旧，于是继续更新Pillow库

[root@demo ~]# pip install --upgrade Pillow
Collecting Pillow
  Downloading Pillow-3.1.0.tar.gz (9.9MB)
    100% |████████████████████████████████| 9.9MB 42kB/s 
Installing collected packages: Pillow
  Found existing installation: Pillow 2.7.0
    Uninstalling Pillow-2.7.0:
      Successfully uninstalled Pillow-2.7.0
  Running setup.py install for Pillow
Successfully installed Pillow-3.1.0

[root@demo ~]# pip install --upgrade Pillow

Collecting Pillow

Downloading Pillow-3.1.0.tar.gz (9.9MB)

100% |████████████████████████████████| 9.9MB 42kB/s

Installing collected packages: Pillow

Found existing installation: Pillow 2.7.0

Uninstalling Pillow-2.7.0:

Successfully uninstalled Pillow-2.7.0

Running setup.py install for Pillow

Successfully installed Pillow-3.1.0

重启odoo服务问题解决
最后回顾了下odoo requirements.txt：
odoo8 Pillow==2.5.1
odoo9 Pillow==2.7.0
其实所谓更新无非是重新安装编译一下Pillow库，没想到直接升级到3.1.0版本，希望没有什么副作用：）

Odoo8、9打印中文字体配置分析详解

源码路径odoo/openerp/report/render/rml2pdf/customfonts.py

# Search path for TTF files, in addition of rl_config.TTFSearchPath
TTFSearchPath = [
            '/usr/share/fonts/truetype', # SuSE
            '/usr/share/fonts/dejavu', '/usr/share/fonts/liberation', # Fedora, RHEL
            '/usr/share/fonts/truetype/*','/usr/local/share/fonts' # Ubuntu,
            '/usr/share/fonts/TTF/*', # Mandriva/Mageia
            '/usr/share/fonts/TTF', # Arch Linux
            '/usr/lib/openoffice/share/fonts/truetype/',
            '~/.fonts',
            '~/.local/share/fonts',

            # mac os X - from
            # http://developer.apple.com/technotes/tn/tn2024.html
            '~/Library/Fonts',
            '/Library/Fonts',
            '/Network/Library/Fonts',
            '/System/Library/Fonts',

            # windows
            'c:/winnt/fonts',
            'c:/windows/fonts'
]

# Search path for TTF files, in addition of rl_config.TTFSearchPath

TTFSearchPath = [

'/usr/share/fonts/truetype', # SuSE

'/usr/share/fonts/dejavu', '/usr/share/fonts/liberation', # Fedora, RHEL

'/usr/share/fonts/truetype/*','/usr/local/share/fonts' # Ubuntu,

'/usr/share/fonts/TTF/*', # Mandriva/Mageia

'/usr/share/fonts/TTF', # Arch Linux

'/usr/lib/openoffice/share/fonts/truetype/',

'~/.fonts',

'~/.local/share/fonts',

# mac os X - from

# http://developer.apple.com/technotes/tn/tn2024.html

'~/Library/Fonts',

'/Library/Fonts',

'/Network/Library/Fonts',

'/System/Library/Fonts',

# windows

'c:/winnt/fonts',

'c:/windows/fonts'

]

可见对于windows、mac及linux大部分发行版的默认系统字体路径都做了比较全面的配置

def list_all_sysfonts():
    """
        This function returns list of font directories of system.
    """
    filepath = []

    # Perform the search for font files ourselves, as reportlab's
    # TTFOpenFile is not very good at it.
    searchpath = list(set(TTFSearchPath + rl_config.TTFSearchPath))
    for dirname in searchpath:
        for filename in glob.glob(os.path.join(os.path.expanduser(dirname), '*.[Tt][Tt][FfCc]')):
            filepath.append(filename)
    return filepath

def list_all_sysfonts():

"""

This function returns list of font directories of system.

"""

filepath = []

# Perform the search for font files ourselves, as reportlab's

# TTFOpenFile is not very good at it.

searchpath = list(set(TTFSearchPath + rl_config.TTFSearchPath))

for dirname in searchpath:

for filename in glob.glob(os.path.join(os.path.expanduser(dirname), '*.[Tt][Tt][FfCc]')):

filepath.append(filename)

return filepath

接着根据正则*.[Tt][Tt][FfCc]对所有配置路径下的文件扩展名做字体匹配以生成odoo可供配置选择的字体列表

一般Linux下使用最多的开源中文字体是文泉译系列，简称wqy，Centos下yum search wqy相关英文描述（中文笔者补充）：

wqy-microhei-fonts.noarch : Compact Chinese fonts derived from Droid
文泉驿微米黑是一个”自由字体”。该字体包含了所有常用简体中文、繁体中文所需要的汉字(最新版本包含超过20932个汉字，完整覆盖GB2312/Big5以及GBK标准字符集)。该字体同时还包含了日文、韩文和其他几十种语言符号。以外，该字体还包含了高质量的Droid Sans拉丁符号和Droid Sans Mono等宽字体，并内置Hinting和Kerning信息。微米黑字体文件极小，特别使用于便携式电脑设备

wqy-unibit-fonts.noarch : WenQuanYi Unibit Bitmap Font
文泉驿Unibit是一款等宽的点阵字体，该字体包含了46,000多个unicode符号，超过27,000多个符合国家标准的汉字点阵字型，是已知的开源字体当中包含符号最完整的字体之一

wqy-zenhei-fonts.noarch : WenQuanYi Zen Hei CJK Font
黑体由于笔画略宽，显示对比度比宋体大，所以越来越得到桌面用户的青睐。文泉驿正黑体正是为这种目的设计的一款开源字体

据上描述可直接根据需要yum install对应的字体名称即可快速安装
当然也可以直接去文泉译官网http://wenq.org/获取最新版本及其它类型中文字体，如文泉驿点阵宋体

然后以优秀的文泉驿微米黑字体为例：

[srj@x1c ~]# rpm -ql wqy-microhei-fonts
/etc/fonts/conf.d/65-wqy-microhei.conf
/usr/share/doc/wqy-microhei-fonts-0.2.0
/usr/share/doc/wqy-microhei-fonts-0.2.0/LICENSE_Apache2.txt
/usr/share/doc/wqy-microhei-fonts-0.2.0/LICENSE_GPLv3.txt
/usr/share/doc/wqy-microhei-fonts-0.2.0/README.txt
/usr/share/fontconfig/conf.avail/65-wqy-microhei.conf
/usr/share/fonts/wqy-microhei
/usr/share/fonts/wqy-microhei/wqy-microhei.ttc

[srj@x1c ~]# rpm -ql wqy-microhei-fonts

/etc/fonts/conf.d/65-wqy-microhei.conf

/usr/share/doc/wqy-microhei-fonts-0.2.0

/usr/share/doc/wqy-microhei-fonts-0.2.0/LICENSE_Apache2.txt

/usr/share/doc/wqy-microhei-fonts-0.2.0/LICENSE_GPLv3.txt

/usr/share/doc/wqy-microhei-fonts-0.2.0/README.txt

/usr/share/fontconfig/conf.avail/65-wqy-microhei.conf

/usr/share/fonts/wqy-microhei

/usr/share/fonts/wqy-microhei/wqy-microhei.ttc

最后一行是字体文件物理位置，很不幸用了独立子目录wqy-microhei，这在官方配置列表里是没有的，不过好在扩展名正则已经支持ttc字体了，之前只有ttf字体才可匹配到，所以很多老教程都是直接在源码里加路径加扩展名匹配来解决

那不改源码最简单的方法就是从配置里与系统最低耦合的~/.fonts用户目录来存放可识别字体：

cp /usr/share/fonts/wqy-microhei/wqy-microhei.ttc ~/.fonts/

1	cp /usr/share/fonts/wqy-microhei/wqy-microhei.ttc ~/.fonts/

最后重启odoo，设置-配置-常规设置-报表字体-重载字体，字体下拉里就可以直接选择或者搜索到WenQuanYi Micro Hei选择并应用生效后即可完美使用中文打印各种报表了

用python-virtualenv统一管理odoo python依赖库

odoo有些python依赖库官方yum源里没有
或者有可能版本不兼容
这就需要根据版本指定安装，默认是安装到
/usr/lib/python2.7/site-packages/
主要是本机开发环境，各种基于python的系统部署一起
长期下来感觉又回到windows时代dll库混乱的悲剧
更何况odoo8和odoo9所依赖的库和版本都不尽相同
非常需要根据应用来独立管理所对应的依赖环境

安装python-virtualenv：

#python-virtualenv.noarch : Tool to create isolated Python environments

sudo yum install python-virtualenv

#python-virtualenv.noarch : Tool to create isolated Python environments

sudo yum install python-virtualenv

创建虚拟环境：

virtualenv --no-site-packages python
New python executable in python/bin/python
Installing Setuptools..............................................................................................................................................................................................................................done.
Installing Pip.....................................................................................................................................................................................................................................................................................................................................done.

virtualenv --no-site-packages python

New python executable in python/bin/python

Installing Setuptools..............................................................................................................................................................................................................................done.

Installing Pip.....................................................................................................................................................................................................................................................................................................................................done.

进入虚拟环境：

[srj@x1c Odoo]$ pwd
/home/srj/Git/Odoo

source ./python/bin/activate

[srj@x1c Odoo]$ pwd

/home/srj/Git/Odoo

source ./python/bin/activate

进入odoo目录直接安装：

(python)[srj@x1c odoo9]$ pwd
/home/srj/Git/Odoo/odoo9

python setup.py install

(python)[srj@x1c odoo9]$ pwd

/home/srj/Git/Odoo/odoo9

python setup.py install

也可以直接通过pip来安装（可用阿里云等提供的国内镜像快速下载）：

cat requirements.txt
Babel==1.3
Jinja2==2.7.3
Mako==1.0.1
MarkupSafe==0.23
Pillow==2.7.0
Python-Chart==1.39
PyYAML==3.11
Werkzeug==0.9.6
argparse==1.2.1
decorator==3.4.0
docutils==0.12
feedparser==5.1.3
gdata==2.0.18
gevent==1.0.2
greenlet==0.4.7
jcconv==0.2.3
lxml==3.4.1
mock==1.0.1
ofxparse==0.14
passlib==1.6.2
psutil==2.2.0
psycogreen==1.0
psycopg2==2.5.4
pyPdf==1.13
pydot==1.0.2
pyparsing==2.0.3
pyserial==2.7
python-dateutil==2.4.0
python-ldap==2.4.19
python-openid==2.2.5
pytz==2014.10
pyusb==1.0.0b2
qrcode==5.1
reportlab==3.1.44
requests==2.6.0
six==1.9.0
suds-jurko==0.6
vatnumber==1.2
vobject==0.6.6
wsgiref==0.1.2
xlwt==0.7.5

pip install -r requirements.txt -i http://mirrors.aliyun.com/pypi/simple/

cat requirements.txt

Babel==1.3

Jinja2==2.7.3

Mako==1.0.1

MarkupSafe==0.23

Pillow==2.7.0

Python-Chart==1.39

PyYAML==3.11

Werkzeug==0.9.6

argparse==1.2.1

decorator==3.4.0

docutils==0.12

feedparser==5.1.3

gdata==2.0.18

gevent==1.0.2

greenlet==0.4.7

jcconv==0.2.3

lxml==3.4.1

mock==1.0.1

ofxparse==0.14

passlib==1.6.2

psutil==2.2.0

psycogreen==1.0

psycopg2==2.5.4

pyPdf==1.13

pydot==1.0.2

pyparsing==2.0.3

pyserial==2.7

python-dateutil==2.4.0

python-ldap==2.4.19

python-openid==2.2.5

pytz==2014.10

pyusb==1.0.0b2

qrcode==5.1

reportlab==3.1.44

requests==2.6.0

six==1.9.0

suds-jurko==0.6

vatnumber==1.2

vobject==0.6.6

wsgiref==0.1.2

xlwt==0.7.5

pip install -r requirements.txt -i http://mirrors.aliyun.com/pypi/simple/

可能会遇到一些库对virtualenv默认的setuptools的版本有要求，根据提示升级下（Centos目前yum源python-virtualenv-1.10.1-2自带的是0.9.8版本有些低）：

easy_install -i http://mirrors.aliyun.com/pypi/simple/ -U setuptools

1	easy_install -i http://mirrors.aliyun.com/pypi/simple/ -U setuptools

同时附上pip、easy_install及setup.py安装获取依赖库的阿里云镜像源配置：

~/.pip/pip.conf
[global]
index-url = http://mirrors.aliyun.com/pypi/simple/

~/.pydistutils.cfg
[easy_install]
index_url = http://mirrors.aliyun.com/pypi/simple/

setup.cfg(setup.py同层目录)
[easy_install]
index_url = http://mirrors.aliyun.com/pypi/simple/

~/.pip/pip.conf

[global]

index-url = http://mirrors.aliyun.com/pypi/simple/

~/.pydistutils.cfg

[easy_install]

index_url = http://mirrors.aliyun.com/pypi/simple/

setup.cfg(setup.py同层目录)

[easy_install]

index_url = http://mirrors.aliyun.com/pypi/simple/

以后每次使用都要先通过source命令指定对应环境下的activate初始化进入
离开则直接使用deactivate命令即可回到原生环境
当然也可以通过修改odoo.py头直接指定虚拟环境的python路径来快捷运行：

[srj@x1c odoo9]$ vim odoo.py
#!/home/srj/Git/Odoo/python/bin/python

1 2	[srj@x1c odoo9]$ vim odoo.py #!/home/srj/Git/Odoo/python/bin/python

odoo.py auto-reload dev自动重启服务ENOSPC系统错误解决

Odoo8：
正常环境下直接–auto-reload参数运行缺库错误

ImportError: No module named pyinotify

1	ImportError: No module named pyinotify

pyinotify是一个Python模块，用来监测文件系统的变化
pyinotify依赖于Linux内核的inotify功能，是一个事件驱动的通知器，其通知接口通过三个系统调用从内核空间到用户空间
pyinotify结合这些系统调用，并提供一个顶级的抽象和一个通用的方式来处理这些功能

安装
pip install pyinotify

运行时错误：

pyinotify.py", line 1943, in add_watch
    self._inotify_wrapper.str_errno()))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8 in position 6: ordinal not in range(128)

pyinotify.py", line 1943, in add_watch

self._inotify_wrapper.str_errno()))

UnicodeDecodeError: 'ascii' codec can't decode byte 0xe8 in position 6: ordinal not in range(128)

Odoo9：
正常环境下直接–dev参数运行日志警告

WARNING ? openerp.service.server: 'watchdog' module not installed. Code autoreload feature is disabled

1	WARNING ? openerp.service.server: 'watchdog' module not installed. Code autoreload feature is disabled

Watchdog是一个跨平台的Python库和shell工具，可以监视文件系统事件。超级好用，并且容易上手

安装
pip install watchdog

运行时错误：

watchdog/observers/inotify_c.py", line 402, in _raise_error
    raise OSError("inotify watch limit reached")
OSError: inotify watch limit reached

watchdog/observers/inotify_c.py", line 402, in _raise_error

raise OSError("inotify watch limit reached")

OSError: inotify watch limit reached

Node：
想起来当初刚玩node时也时常会遇到这个错误
不过大多直接sudo运行就可解决，简单理解权限问题也没有深究
但是odoo不能这么搞，源码限制：

Running as user 'root' is a security risk, aborting.

1	Running as user 'root' is a security risk, aborting.

还好从odoo9的报错信息里显而易见问题出自底层inotify对一般用户的限制
简单学习了下，得知其有个max_user_watches的内核参数限制普通用户一次最多关联监控个数。一般默认值8192，对于odoo这种大工程或稍大一点的node项目来说明显是不够用的

先通过如下方式验证：

[srj@x1c /]$ cat /proc/sys/fs/inotify/max_user_watches
8192

1 2	[srj@x1c /]$ cat /proc/sys/fs/inotify/max_user_watches 8192

然后通过su切换root身份动态更新配置值放大64倍

[srj@x1c /]$ su -c 'echo 524288 > /proc/sys/fs/inotify/max_user_watches'

1	[srj@x1c /]$ su -c 'echo 524288 > /proc/sys/fs/inotify/max_user_watches'

接着用不同版本的启动参数运行即可看到AutoReload watcher running成功了

INFO ? openerp.service.server: Watching addons folder /home/srj/.local/share/Odoo/addons/8.0
INFO ? openerp.service.server: AutoReload watcher running

1 2	INFO ? openerp.service.server: Watching addons folder /home/srj/.local/share/Odoo/addons/8.0 INFO ? openerp.service.server: AutoReload watcher running

最后还需要将动态修改的参数通过静态配置方式固化下来，否则每次重启还需要重复修改
Centos7下我不建议直接修改/etc/sysctl.conf文件配置，而是通过sysctl.d目录新建独立配置

[root@x1c sysctl.d]# pwd
/etc/sysctl.d
[root@x1c sysctl.d]# echo fs.inotify.max_user_watches = 524288 > 91-inotify.conf 
[root@x1c sysctl.d]# cat 91-inotify.conf 
fs.inotify.max_user_watches = 524288

[root@x1c sysctl.d]# pwd

/etc/sysctl.d

[root@x1c sysctl.d]# echo fs.inotify.max_user_watches = 524288 > 91-inotify.conf

[root@x1c sysctl.d]# cat 91-inotify.conf

fs.inotify.max_user_watches = 524288

然后重新启动或者使用

[root@x1c sysctl.d]# sysctl --system
* Applying /etc/sysctl.d/91-inotify.conf ...
fs.inotify.max_user_watches = 524288
* Applying /etc/sysctl.conf ...

[root@x1c sysctl.d]# sysctl --system

* Applying /etc/sysctl.d/91-inotify.conf ...

fs.inotify.max_user_watches = 524288

* Applying /etc/sysctl.conf ...

sysctl命令system参数立刻生效

Linux centos yum install odoo rpm postinstall scriptlet

众所周知，odoo官方提供了非常方便的yum安装源用于一键安装
只需先根据版本配置源

odoo8

yum-config-manager --add-repo=https://nightly.odoo.com/8.0/nightly/rpm/odoo.repo

1	yum-config-manager --add-repo=https://nightly.odoo.com/8.0/nightly/rpm/odoo.repo

odoo9

yum-config-manager --add-repo=https://nightly.odoo.com/9.0/nightly/rpm/odoo.repo

1	yum-config-manager --add-repo=https://nightly.odoo.com/9.0/nightly/rpm/odoo.repo

之后即可一键自动解决依赖安装

yum install -y odoo

1	yum install -y odoo

相信源码安装过的同学都一定很好奇
这么繁琐复杂的细节居然可以全部包装到一个rpm包里透明掉了
还有那么多依赖库，怎么可能yum里全部都有
带着这种疑问认真研究了下
才知道rpm包内除了相应的程序，还可能有pre和post install两个shell脚本
分别对应安装前和安装后执行
以下为8.0版本latest rpm包为例，其中文注释为本人补充方便整体理解

rpm -qp --scripts odoo_8.0.latest.noarch.rpm
postinstall scriptlet (using /bin/sh):
#!/bin/sh
#错误立即退出
set -e
#配置目录
ODOO_CONFIGURATION_DIR=/etc/odoo
#配置文件
ODOO_CONFIGURATION_FILE=$ODOO_CONFIGURATION_DIR/openerp-server.conf
#数据目录
ODOO_DATA_DIR=/var/lib/odoo
ODOO_GROUP="odoo"
#日志目录
ODOO_LOG_DIR=/var/log/odoo
ODOO_USER="odoo"
#创建系统用户及用户组
if ! getent passwd | grep -q "^odoo:"; then
    groupadd $ODOO_GROUP
    adduser --system --no-create-home $ODOO_USER -g $ODOO_GROUP
fi
# Register "$ODOO_USER" as a postgres user with "Create DB" role attribute
su - postgres -c "createuser -d -R -S $ODOO_USER" 2> /dev/null || true
# Configuration file
mkdir -p $ODOO_CONFIGURATION_DIR
# can't copy debian config-file as addons_path is not the same
echo "[options]
; This is the password that allows database operations:
; admin_passwd = admin
db_host = False
db_port = False
db_user = $ODOO_USER
db_password = False
addons_path = /usr/lib/python2.7/site-packages/openerp/addons
" > $ODOO_CONFIGURATION_FILE
#配置文件权限设置
chown $ODOO_USER:$ODOO_GROUP $ODOO_CONFIGURATION_FILE
chmod 0640 $ODOO_CONFIGURATION_FILE
# Log
mkdir -p $ODOO_LOG_DIR
chown $ODOO_USER:$ODOO_GROUP $ODOO_LOG_DIR
chmod 0750 $ODOO_LOG_DIR
# Data dir
mkdir -p $ODOO_DATA_DIR
chown $ODOO_USER:$ODOO_GROUP $ODOO_DATA_DIR
#系统服务
INIT_FILE=/lib/systemd/system/odoo.service
touch $INIT_FILE
chmod 0700 $INIT_FILE
cat << 'EOF' > $INIT_FILE
[Unit]
Description=Odoo Open Source ERP and CRM
After=network.target

[Service]
Type=simple
User=odoo
Group=odoo
ExecStart=/usr/bin/odoo.py --config=/etc/odoo/openerp-server.conf

[Install]
WantedBy=multi-user.target
EOF
#YUM中没有的Python依赖库部分
easy_install pyPdf vatnumber pydot psycogreen

rpm -qp --scripts odoo_8.0.latest.noarch.rpm

postinstall scriptlet (using /bin/sh):

#!/bin/sh

#错误立即退出

set -e

#配置目录

ODOO_CONFIGURATION_DIR=/etc/odoo

#配置文件

ODOO_CONFIGURATION_FILE=$ODOO_CONFIGURATION_DIR/openerp-server.conf

#数据目录

ODOO_DATA_DIR=/var/lib/odoo

ODOO_GROUP="odoo"

#日志目录

ODOO_LOG_DIR=/var/log/odoo

ODOO_USER="odoo"

#创建系统用户及用户组

if ! getent passwd | grep -q "^odoo:"; then

groupadd $ODOO_GROUP

adduser --system --no-create-home $ODOO_USER -g $ODOO_GROUP

# Register "$ODOO_USER" as a postgres user with "Create DB" role attribute

su - postgres -c "createuser -d -R -S $ODOO_USER" 2> /dev/null || true

# Configuration file

mkdir -p $ODOO_CONFIGURATION_DIR

# can't copy debian config-file as addons_path is not the same

echo "[options]

; This is the password that allows database operations:

; admin_passwd = admin

db_host = False

db_port = False

db_user = $ODOO_USER

db_password = False

addons_path = /usr/lib/python2.7/site-packages/openerp/addons

" > $ODOO_CONFIGURATION_FILE

#配置文件权限设置

chown $ODOO_USER:$ODOO_GROUP $ODOO_CONFIGURATION_FILE

chmod 0640 $ODOO_CONFIGURATION_FILE

# Log

mkdir -p $ODOO_LOG_DIR

chown $ODOO_USER:$ODOO_GROUP $ODOO_LOG_DIR

chmod 0750 $ODOO_LOG_DIR

# Data dir

mkdir -p $ODOO_DATA_DIR

chown $ODOO_USER:$ODOO_GROUP $ODOO_DATA_DIR

#系统服务

INIT_FILE=/lib/systemd/system/odoo.service

touch $INIT_FILE

chmod 0700 $INIT_FILE

cat << 'EOF' > $INIT_FILE

[Unit]

Description=Odoo Open Source ERP and CRM

After=network.target

[Service]

Type=simple

User=odoo

Group=odoo

ExecStart=/usr/bin/odoo.py --config=/etc/odoo/openerp-server.conf

[Install]

WantedBy=multi-user.target

EOF

#YUM中没有的Python依赖库部分

easy_install pyPdf vatnumber pydot psycogreen

可见诸多内幕与细节全都在这段脚本里完美体现了
知己知彼，剖析清楚每一行代码后，对基于源代码的个性化定制安装部署又有了新的认识

Linux Centos7 ThinkPad X1C无线网卡问题解决记录

折腾了两天，总结下问题
不知是2015款才有的问题还是前面几代内置无线网卡型号不同而不同

话说刚装Centos7系统时
安装向导顺利适配无线网卡并顺畅连接无线网络完成整个安装过程
然而在正常启动登录后，网卡是不适配的，当然除此之外其它驱动都完美适配

初步判断是安装向导自带很多无线驱动
但这些不是全都默认安装的，不过好歹知道是肯定支持的就放心了

查阅大量相关社区讨论及文档阅读后
最终发现这款型号Intel Wireless-N 7265 BN的驱动官方yum源就有：

iwl7265-firmware.noarch : Firmware for Intel(R) Dual Band Wireless-AC 7265: Series Adapters

1	iwl7265-firmware.noarch : Firmware for Intel(R) Dual Band Wireless-AC 7265: Series Adapters

由于无网络连有线口都没，只好先去台式机用yum只下载不安装

sudo yum install --downloadonly --downloaddir=/home/srj/Downloads iwl7265-firmware

1	sudo yum install --downloadonly --downloaddir=/home/srj/Downloads iwl7265-firmware

得到iwl7265-firmware-22.0.7.0-36.el7.noarch.rpm安装包后通过U盘拷贝到小C本地安装

sudo yum localinstall iwl7265-firmware-22.0.7.0-36.el7.noarch.rpm

1	sudo yum localinstall iwl7265-firmware-22.0.7.0-36.el7.noarch.rpm

重启后无线网络的小图标久别重逢了
但是好景不长就发现网络虽能连接但及其不稳定
掉包效超高，断线率也不少，经常动不动就全没了
回想安装向导时那驱动还是很稳定服务的，只能怀疑驱动版本问题了，毕竟小C内置的不是双频AC网卡，当然这要在Windows下肯定是一个大驱动全包了

接着又搜寻了许久，最终在
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
找到了传说中Intel全系列Linux Wireless Driver下载集中地

然后根据Centos7 Kernel 3.10旧内核版本比较其实都不匹配
最终比对了下之前yum源安装的驱动

[srj@x1c firmware]$ pwd
/usr/lib/firmware
[srj@x1c firmware]$ ll|grep 7265
-rw-r--r--. 1 root root  690452 8月   9 23:40 iwlwifi-7265-8.ucode
-rw-r--r--. 1 root root  697828 8月   9 23:47 iwlwifi-7265-9.ucode