~ubuntu-branches/ubuntu/trusty/eclipse-linuxtools/trusty

<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<head>

<title>Specfile Editor User Guide - General Usage</title>

</head>

<body>

<tr>

<th style="width: 100%" align="center" colspan="3">General Usage</th>

</tr>

<tr>

</a>

</td>

</a>

</td>

</tr>

<tr>

<td style="width: 20%" align="left" valign="top">Installing</td>

<td style="width: 20%" align="right" valign="top">Import src.rpm and export rpm and src.rpm</td>

</tr>

</table><hr/>

<h1 id="General_Usage">General Usage</h1>

To fully benefit from all the features offered by the Specfile Editor, ensure that your

<code>.spec</code> file is part of a project inside the Eclipse workspace. <code>rpmlint</code> integration, file hyperlinks, and some auto-completion features are not available otherwise. The following screenshot provides an impression of the full interface benefits provided by the Specfile Editor plug-in:

<h2 id="Creating_a_New_RPM_project">Creating a New RPM project</h2>

<h2 id="Creating_a_New_Specfile">Creating a New Specfile</h2>

The Specfile Editor plug-in provides a wizard for creating new

<code>.spec</code> files. To use this wizard, navigate first to File > New > Other... ; then, expand the RPM Wizards entry to select New specfile based on a template.

This will open the Specfile Creation wizard, which provides an interface for generating the basic contents of a

<code>.spec</code> file.

The Specfile Creation wizard contains the following fields:

<dl>

<dt>Project</dt>

<dd>This field associates the generated

<code>.spec</code> with a project in the current workspace, which ultimately specifies where the

<code>.spec</code> will be saved. The

Select a project...

button allows you to select a specific project for this field with ease. By default, the Specfile Editor plug-in specifies the last active project when you invoked the Specfile Creation wizard.

</dd>

</dl>

<dl>

<dt>Select a template </dt>

<dd>This drop-down list allows you to select a

<code>.spec</code> template to use. You can install templates provided by <code>rpmdevtools</code>, which is available

<a href="https://fedorahosted.org/rpmdevtools">https://fedorahosted.org/rpmdevtools</a> .

</dd>

</dl>

<dl>

<dt>Version </dt>

<dd>This fills in the <code>Version:</code> line of the

<code>.spec</code> file.

</dd>

</dl>

<dl>

<dt>Summary </dt>

<dd>This fills in the <code>Summary:</code> line of the

<code>.spec</code> file.

</dd>

</dl>

<dl>

<dt>Group </dt>

<dd>This drop-down list allows you to select a package group to which the project belongs.</dd>

</dl>

<dl>

<dt>License </dt>

<dd>This fills in the <code>License:</code> line of the

<code>.spec</code> file.

</dd>

</dl>

<dl>

<dd>This fills in the <code>URL:</code> line of the

<code>.spec</code> file, which typically specifies the public home page of the project.

</dd>

</dl>

<dl>

<dt>Source0 </dt>

100

<dd>This field specifies the source archive from which the package is built.</dd>

101

</dl>

102

<h2 id="rpmlint">rpmlint</h2>

103

To enable <code>rpmlint</code> warnings, right-click on the project containing the

104

<code>.spec</code> file. Then, select Add/Remove rpmlint warnings from the context menu. You can use this menu selection to disable <code>rpmlint</code> warnings as well.

105

106

107

108

109

Enabling <code>rpmlint</code> warnings will add a new <code>rpmlint</code> builder to the project. This <code>rpmlint</code> builder checks the

110

<code>.spec</code> file during each project build or clean. Afterwards, the builder displays any appropriate warnings and errors in the

111

112

Problems

113

pane. Each warning/error is plotted in the

114

<code>.spec</code> file as well; clicking an <code>rpmlint</code> warning/error in the

115

116

Problems

117

pane will automatically place the insertion point on the corresponding section in the

118

<code>.spec</code> file.

119

120

121

122

123

<h3 id="Quick_Fixes">Quick Fixes</h3>

124

You can also directly resolve several warnings and errors through the

125

126

Quick Fix

127

menu. To access this menu, right-click on a warning or error from the

128

129

Problems

130

pane and select Quick Fix.

131

132

As the name suggests, the

133

134

Quick Fix

135

menu provides you with quick solutions to common

136

<code>.spec</code> file errors and problems. For example, <code>rpmlint</code> detected a <code>no-cleaning-of-buildroot</code> error in the following <code>%install</code> section from the <code>.spec</code> file:

137

138

139

140

141

If the

142

143

Quick Fix

144

menu can provide a solution for a particular error, it will be available in the menu. To apply it, simply select the solution (from the

145

146

Select a fix:

147

area) and the corresponding problem (from the

148

149

Problems:

150

area), then click the Finish button.

151

152

153

154

155

The following screenshot shows the revisions to the <code>%install</code> section applied by the

156

157

Quick Fix

158

menu:

159

160

161

162

<hr/>

163

164

<tr>

165

166

167

168

</a>

169

</td>

170

171

172

173

</a>

174

</td>

175

176

177

178

</a>

179

</td>

180

</tr>

181

<tr>

182

<td style="width: 20%" align="left" valign="top">Installing</td>

183

184

<td style="width: 20%" align="right" valign="top">Import src.rpm and export rpm and src.rpm</td>

185

</tr>

186

</table>

187

</body>

188

</html>

b'\\ No newline at end of file'

Older »