Packaged rpm package - making RPM packages

This software-defined domain name. 2. Version: This field defines the version number. Only when there is a greater change than the previous software version number increase. Note: The version number can not contain the minus sign (-) characters. 3. Release: This field defines the release number. If the software is small change compared with the previous, only increased release number does not change the version number. Note: The release number also can not contain the minus sign (-) characters. RPM using the above Name (software name), Version (version number), Release (release number) and the number of named package system, as in this example the output file is named wrapped lze-6.0-2.i386.rpm. 4. Summary: This field defines the package profile, one sentence description. 5. Group: This field defines Category software, see>, the present embodiment Applications / Editors showing the software is a "application / Editor" class. 6. License :( former is Copyright, now generally do not support this interpretation) This field defines the applicable software license or copyright rules. The domain is also available Copyright (copyright) to define, both agree. There are specific license: GPL (General Public License, a free software applicable), BSD, MIT, Public Domain (public domain), Distributable (contribution), Commercial (business), Share (share) and other functions necessary to explain: 1.% this is described in paragraph description section, the content section is to be more detailed description of package, unlike the Summary header fields only word instructions. Free text description, can be any wrapping, is not limited. 2.% prep This is a pretreatment section, which reads pre-script. The program complete the following tasks: * build software compiled with the directory; * the source code decompression; * by patching, upgrade the source code; * perform some other operations, the source code can be compiled at any time. 3.% build script compiler connection (Build) which started the installation file 4.% install script (the install) 5.% files started in this paragraph is a file segment, which defines the package needs to include. This end of the file segments typically described in order to add the file name for easy editing. 6.% defattr (-, root, root)% defattr (rights, owner, is a group) wherein: permissions, the owner and group can use the minus sign (-). Use minus attributes set by the system. For example:% defattr (022, zzz, zhsoft) is set for all subsequent file permissions 022, the owner is ZZZ, is a group of zhsoft; Another example:% defattr (-, zzz, -) is set thereafter All the main document for the zzz, privileges and is a group set up by the system. 7.% doc This modifier set the file type for the documentation 8.% changelog content format: * day week month year to maintain the content Note: Each maintenance records are * beginning, week, month shall be for the abbreviation. Branches can maintain the content for a long time to write a reference http://linux.chinaunix.net/techdoc/system/2006/03/09/928764.shtml

Reproduced in: https: //my.oschina.net/766/blog/211197

Guess you like

Origin blog.csdn.net/weixin_33965305/article/details/91493005