]>
Commit | Line | Data |
---|---|---|
d2cae66f | 1 | # TODO |
e71cf32a | 2 | # - sumaries for subpackages |
3 | # - dependencies | |
f111a2c5 | 4 | %include /usr/lib/rpm/macros.php |
366e32c5 | 5 | Summary: Zend Framework |
4bcf46e1 | 6 | Summary(pl.UTF-8): Szkielet Zend |
366e32c5 | 7 | Name: ZendFramework |
07279f88 | 8 | Version: 1.6.1 |
e71cf32a | 9 | Release: 1 |
e100c5ce | 10 | License: New BSD License |
366e32c5 | 11 | Group: Development/Languages/PHP |
d2cae66f | 12 | Source0: http://framework.zend.com/releases/%{name}-%{version}/ZendFramework-%{version}.tar.gz |
07279f88 | 13 | # Source0-md5: 1f41af0cc0f13ea436c6d7f0e2e76923 |
366e32c5 | 14 | URL: http://framework.zend.com/ |
f111a2c5 | 15 | BuildRequires: rpm-php-pearprov >= 4.4.2-11 |
6e96c14e | 16 | Requires: php-common >= 4:5.1.4 |
d2cae66f ER |
17 | Requires: php-ctype |
18 | Requires: php-hash | |
19 | Requires: php-iconv | |
20 | Requires: php-pcre | |
21 | Requires: php-pdo | |
6e96c14e | 22 | Obsoletes: ZendFramework-doc |
366e32c5 ER |
23 | BuildArch: noarch |
24 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) | |
25 | ||
366e32c5 ER |
26 | %description |
27 | Zend Framework is a high quality and open source framework for | |
28 | developing Web Applications and Web Services. | |
29 | ||
30 | Built in the true PHP spirit, the Zend Framework delivers ease-of-use | |
31 | and powerful functionality. It provides solutions for building modern, | |
32 | robust, and secure websites. | |
33 | ||
0c96b98d JR |
34 | %description -l pl.UTF-8 |
35 | Zend Framework to mający otwarte źródła, wysokiej jakości szkielet do | |
36 | tworzenia aplikacji i usług WWW. | |
6dcfea62 | 37 | |
0c96b98d JR |
38 | Stworzony w prawdziwym duchu PHP szkielet Zend dostarcza łatwą w |
39 | użyciu i potężną funkcjonalność. Udostępnia rozwiązania do tworzenia | |
40 | nowoczesnych, bogatych i bezpiecznych serwisów WWW. | |
6dcfea62 | 41 | |
e71cf32a | 42 | %package Zend_Acl |
43 | Summary: Zend_Acl | |
44 | Group: Development/Languages/PHP | |
45 | URL: http://framework.zend.com/manual/en/zend.acl.html | |
46 | Requires: %{name} = %{version}-%{release} | |
47 | ||
48 | %description Zend_Acl | |
49 | Zend_Acl provides lightweight and flexible access control list (ACL) | |
50 | functionality and privileges management. In general, an application | |
51 | may utilize such functionality to control access to certain protected | |
52 | objects by other requesting objects. | |
53 | ||
54 | %package Zend_Auth | |
55 | Summary: Zend_Auth | |
56 | Group: Development/Languages/PHP | |
57 | URL: http://framework.zend.com/manual/en/zend.auth.html | |
58 | Requires: %{name} = %{version}-%{release} | |
59 | ||
60 | %description Zend_Auth | |
61 | Zend_Auth provides an API for authentication and includes concrete | |
62 | authentication adapters for common use case scenarios. | |
63 | ||
64 | %package Zend_Cache | |
65 | Summary: Zend_Cache | |
66 | Group: Development/Languages/PHP | |
67 | URL: http://framework.zend.com/manual/en/zend.cache.html | |
68 | Requires: %{name} = %{version}-%{release} | |
69 | ||
70 | %description Zend_Cache | |
71 | Zend_Cache provides a flexible approach toward caching data, including | |
72 | support for tagging, manipulating, iterating, and removing subsets. | |
73 | ||
74 | %package Zend_Captcha | |
75 | Summary: Zend_Captcha | |
76 | Group: Development/Languages/PHP | |
77 | URL: http://framework.zend.com/manual/en/zend.captcha.html | |
78 | Requires: %{name} = %{version}-%{release} | |
79 | ||
80 | %description Zend_Captcha | |
81 | CAPTCHA stands for "Completely Automated Turing test to tell Computers | |
82 | and Humans Apart" it is used as a challenge-response to ensure that | |
83 | the individual submitting information is a human and not an automated | |
84 | process. Typically, a captcha is used with form submissions where | |
85 | authenticated users are not necessary, but you desire to prevent spam | |
86 | submissions. Captchas can take variety of forms, including asking | |
87 | logic questions, presenting skewed fonts, and presenting images and | |
88 | asking how they relate. Zend_Captcha aims to provide a variety of | |
89 | backends that may be utilized either standalone or in conjunction with | |
90 | Zend_Form. | |
91 | ||
92 | %package Zend_Config | |
93 | Summary: Zend_Config | |
94 | Group: Development/Languages/PHP | |
95 | URL: http://framework.zend.com/manual/en/zend.config.html | |
96 | Requires: %{name} = %{version}-%{release} | |
97 | ||
98 | %description Zend_Config | |
99 | Zend_Config is designed to simplify access to and use of configuration | |
100 | data within applications. | |
101 | ||
102 | %package Zend_Console_Getopt | |
103 | Summary: Zend_Console_Getopt | |
104 | Group: Development/Languages/PHP | |
105 | URL: http://framework.zend.com/manual/en/zend.console.getopt.html | |
106 | Requires: %{name} = %{version}-%{release} | |
107 | ||
108 | %description Zend_Console_Getopt | |
109 | The Zend_Console_Getopt class helps command-line applications to parse | |
110 | their options and arguments. | |
111 | ||
112 | %package Zend_Controller | |
113 | Summary: Zend_Controller | |
114 | Group: Development/Languages/PHP | |
115 | URL: http://framework.zend.com/manual/en/zend.controller.html | |
116 | Requires: %{name} = %{version}-%{release} | |
117 | ||
118 | %description Zend_Controller | |
119 | Zend_Controller is the heart of Zend Framework's MVC system. MVC | |
120 | stands for Model-View-Controller and is a design pattern targeted at | |
121 | separating application logic from display logic. | |
122 | ||
123 | %package Zend_Currency | |
124 | Summary: Zend_Currency | |
125 | Group: Development/Languages/PHP | |
126 | URL: http://framework.zend.com/manual/en/zend.currency.html | |
127 | Requires: %{name} = %{version}-%{release} | |
128 | ||
129 | %description Zend_Currency | |
130 | Zend_Currency is part of the I18N core of the Zend_Framework. It | |
131 | handles all issues related to currency, money representation and | |
132 | formating. And it also provides additional informational methods which | |
133 | include localized informations on currencies, informations about which | |
134 | currency is used in which region and more. | |
135 | ||
136 | %package Zend_Date | |
137 | Summary: Zend_Date | |
138 | Group: Development/Languages/PHP | |
139 | URL: http://framework.zend.com/manual/en/zend.date.html | |
140 | Requires: %{name} = %{version}-%{release} | |
141 | ||
142 | %description Zend_Date | |
143 | Zend_Date component offers a detailed, but simple API for manipulating | |
144 | dates and times. Its methods accept a wide variety of types of | |
145 | information, including date parts, in numerous combinations yielding | |
146 | many features and possibilities above and beyond the existing PHP date | |
147 | related functions. | |
148 | ||
149 | %package Zend_Db | |
150 | Summary: Zend_Db | |
151 | Group: Development/Languages/PHP | |
152 | URL: http://framework.zend.com/manual/en/zend.db.html | |
153 | Requires: %{name} = %{version}-%{release} | |
154 | ||
155 | %description Zend_Db | |
156 | Zend_Db and its related classes provide a simple SQL database | |
157 | interface for Zend Framework. The Zend_Db_Adapter is the basic class | |
158 | you use to connect your PHP application to an RDBMS. There is a | |
159 | different Adapter class for each brand of RDBMS. The Zend_Db Adapters | |
160 | create a bridge from the vendor-specific PHP extensions to a common | |
161 | interface, to help you write PHP applications once and deploy with | |
162 | multiple brands of RDBMS with very little effort. The interface of the | |
163 | Adapter class is similar to the interface of the PHP Data Objects | |
164 | extension. | |
165 | ||
166 | Zend_Db provides Adapter classes to PDO drivers for the following | |
167 | RDBMS brands: | |
168 | - IBM DB2 and Informix Dynamic Server (IDS), using the pdo_ibm PHP | |
169 | extension | |
170 | - MySQL, using the pdo_mysql PHP extension | |
171 | - Microsoft SQL Server, using the pdo_mssql PHP extension | |
172 | - Oracle, using the pdo_oci PHP extension | |
173 | - PostgreSQL, using the pdo_pgsql PHP extension | |
174 | - SQLite, using the pdo_sqlite PHP extension | |
175 | ||
176 | In addition, Zend_Db provides Adapter classes that utilize PHP | |
177 | database extensions for the following RDBMS brands: | |
178 | - MySQL, using the mysqli PHP extension | |
179 | - Oracle, using the oci8 PHP extension | |
180 | - IBM DB2, using the ibm_db2 PHP extension | |
181 | - Firebird/Interbase, using the php_interbase PHP extension | |
182 | ||
183 | %package Zend_Debug | |
184 | Summary: Zend_Debug | |
185 | Group: Development/Languages/PHP | |
186 | URL: http://framework.zend.com/manual/en/zend.debug.html | |
187 | Requires: %{name} = %{version}-%{release} | |
188 | ||
189 | %description Zend_Debug | |
190 | Zend_Debug is a simple debugging component. The static method | |
191 | Zend_Debug::dump() prints or returns information about an expression. | |
192 | This simple technique of debugging is easy to use in an ad hoc | |
193 | fashion, and requires no initialization, special tools, or debugging | |
194 | environment. | |
195 | ||
196 | %package Zend_Dojo | |
197 | Summary: Zend_Dojo | |
198 | Group: Development/Languages/PHP | |
199 | URL: http://framework.zend.com/manual/en/zend.dojo.html | |
200 | Requires: %{name} = %{version}-%{release} | |
201 | ||
202 | %description Zend_Dojo | |
203 | Zend_Dojo component provides integration with Dojo Toolkit. | |
204 | ||
205 | Integration points with Dojo include: | |
206 | - JSON-RPC support | |
207 | - dojo.data compatibility | |
208 | - View helper to help setup the Dojo environment | |
209 | - Dijit-specific Zend_View helpres | |
210 | - Dijit-specific Zend_Form elements and decorators | |
211 | ||
212 | %package Zend_Dom | |
213 | Summary: Zend_Dom | |
214 | Group: Development/Languages/PHP | |
215 | URL: http://framework.zend.com/manual/en/zend.dom.html | |
216 | Requires: %{name} = %{version}-%{release} | |
217 | ||
218 | %description Zend_Dom | |
219 | Zend_Dom provides tools for working with DOM documents and structures. | |
220 | Currently, it offer Zend_Dom_Query, which provides a unified interface | |
221 | for querying DOM documents utilizing both XPath and CSS selectors. | |
222 | ||
223 | %package Zend_Exception | |
224 | Summary: Zend_Exception | |
225 | Group: Development/Languages/PHP | |
226 | URL: http://framework.zend.com/manual/en/zend.exception.html | |
227 | Requires: %{name} = %{version}-%{release} | |
228 | ||
229 | %description Zend_Exception | |
230 | Zend_Exception is a base exception class. All exceptions thrown by | |
231 | Zend Framework classes should throw an exception that derives from the | |
232 | base class Zend_Exception. | |
233 | ||
234 | %package Zend_Feed | |
235 | Summary: Zend_Feed | |
236 | Group: Development/Languages/PHP | |
237 | URL: http://framework.zend.com/manual/en/zend.feed.html | |
238 | Requires: %{name} = %{version}-%{release} | |
239 | ||
240 | %description Zend_Feed | |
241 | Zend_Feed provides functionality for consuming RSS and Atom feeds. It | |
242 | provides a natural syntax for accessing elements of feeds, feed | |
243 | attributes, and entry attributes. Zend_Feed also has extensive support | |
244 | for modifying feed and entry structure with the same natural syntax, | |
245 | and turning the result back into XML. In the future, this modification | |
246 | support could provide support for the Atom Publishing Protocol. | |
247 | ||
248 | %package Zend_File | |
249 | Summary: Zend_File | |
250 | Group: Development/Languages/PHP | |
251 | URL: http://framework.zend.com/manual/en/zend.file.html | |
252 | Requires: %{name} = %{version}-%{release} | |
253 | ||
254 | %description Zend_File | |
255 | Zend_File enables developers to take control over file uploads and | |
256 | also over file downloads. It allows you to use built in validators for | |
257 | file purposes and gives you the ability even to change files with | |
258 | filters. Zend_File_Transfer works with adapters which allow to use the | |
259 | same API for different transport protocols like HTTP, FTP, WEBDAV and | |
260 | more. | |
261 | ||
262 | %package Zend_Filter | |
263 | Summary: Zend_Filter | |
264 | Group: Development/Languages/PHP | |
265 | URL: http://framework.zend.com/manual/en/zend.filter.html | |
266 | Requires: %{name} = %{version}-%{release} | |
267 | ||
268 | %description Zend_Filter | |
269 | Zend_Filter component provides a set of commonly needed data filters. | |
270 | It also provides a simple filter chaining mechanism by which multiple | |
271 | filters may be applied to a single datum in a user-defined order. | |
272 | ||
273 | %package Zend_Filter_Input | |
274 | Summary: Zend_Filter_Input | |
275 | Group: Development/Languages/PHP | |
276 | URL: http://framework.zend.com/manual/en/zend.filter.input.html | |
277 | Requires: %{name} = %{version}-%{release} | |
278 | ||
279 | %description Zend_Filter_Input | |
280 | Zend_Filter_Input provides a declarative interface to associate | |
281 | multiple filters and validators, apply them to collections of data, | |
282 | and to retrieve input values after they have been processed by the | |
283 | filters and validators. Values are returned in escaped format by | |
284 | default for safe HTML output. | |
285 | ||
286 | %package Zend_Form | |
287 | Summary: Zend_Form | |
288 | Group: Development/Languages/PHP | |
289 | URL: http://framework.zend.com/manual/en/zend.form.html | |
290 | Requires: %{name} = %{version}-%{release} | |
291 | ||
292 | %description Zend_Form | |
293 | Zend_Form simplifies form creation and handling in your web | |
294 | application. It accomplishes the following goals: | |
295 | - Element input filtering and validation | |
296 | - Element ordering | |
297 | - Element and Form rendering, including escaping | |
298 | - Element and form grouping | |
299 | - Element and form-level configuration | |
300 | ||
301 | %package Zend_Gdata | |
302 | Summary: Zend_Gdata | |
303 | Group: Development/Languages/PHP | |
304 | URL: http://framework.zend.com/manual/en/zend.gdata.html | |
305 | Requires: %{name} = %{version}-%{release} | |
306 | ||
307 | %description Zend_Gdata | |
308 | Zend_Gdata component is a interface for accessing Google Data from | |
309 | PHP. Google Data APIs provide programmatic interface to some of | |
310 | Google's online services. The Google data Protocol is based upon the | |
311 | Atom Publishing Protocol and allows client applications to retrieve | |
312 | data matching queries, post data, update data and delete data using | |
313 | standard HTTP and the Atom syndication formation. Zend_Gdata component | |
314 | also supports accessing other services implementing the Atom | |
315 | Publishing Protocol. | |
316 | ||
317 | %package Zend_Http | |
318 | Summary: Zend_Http | |
319 | Group: Development/Languages/PHP | |
320 | URL: http://framework.zend.com/manual/en/zend.http.html | |
321 | Requires: %{name} = %{version}-%{release} | |
322 | ||
323 | %description Zend_Http | |
324 | Zend_Http component provides a client for the HTTP protocol. It | |
325 | supports: | |
326 | - URL validation | |
327 | - cookies | |
328 | - proxy servers. | |
329 | ||
330 | %package Zend_InfoCard | |
331 | Summary: Zend_InfoCard | |
332 | Group: Development/Languages/PHP | |
333 | URL: http://framework.zend.com/manual/en/zend.infocard.html | |
334 | Requires: %{name} = %{version}-%{release} | |
335 | ||
336 | %description Zend_InfoCard | |
337 | Zend_InfoCard component implements relying-party support for | |
338 | Information Cards. Infomation Cards are used for identity management | |
339 | on the internet and authentication of users to web sites (called | |
340 | relying parties). | |
341 | ||
342 | %package Zend_Json | |
343 | Summary: Zend_Json | |
344 | Group: Development/Languages/PHP | |
345 | URL: http://framework.zend.com/manual/en/zend.json.html | |
346 | Requires: %{name} = %{version}-%{release} | |
347 | ||
348 | %description Zend_Json | |
349 | Zend_Json provides convenience methods for serializing native PHP to | |
350 | JSON and decoding JSON to native PHP. | |
351 | ||
352 | JSON, JavaScript Object Notation, can be used for data interchange | |
353 | between JavaScript and other languages. Since JSON can be directly | |
354 | evaluated by JavaScript, it is a more efficient and lightweight format | |
355 | than XML for exchanging data with JavaScript clients. | |
356 | ||
357 | In addition, Zend_Json provides a useful way to convert any arbitrary | |
358 | XML formatted string into a JSON formatted string. This built-in | |
359 | feature will enable PHP developers to transform the enterprise data | |
360 | encoded in XML format into JSON format before sending it to | |
361 | browser-based Ajax client applications. It provides an easy way to do | |
362 | dynamic data conversion on the server-side code thereby avoiding | |
363 | unnecessary XML parsing in the browser-side applications. It offers a | |
364 | nice utility function that results in easier application-specific data | |
365 | processing techniques. | |
366 | ||
367 | %package Zend_Layout | |
368 | Summary: Zend_Layout | |
369 | Group: Development/Languages/PHP | |
370 | URL: http://framework.zend.com/manual/en/zend.layout.html | |
371 | Requires: %{name} = %{version}-%{release} | |
372 | ||
373 | %description Zend_Layout | |
374 | Zend_Layout implements a classic Two Step View pattern, allowing | |
375 | developers to wrap application content within another view, usually | |
376 | representing the site template. Such templates are often termed | |
377 | layouts by other projects, and Zend Framework has adopted this term | |
378 | for consistency. | |
379 | ||
380 | The main goals of Zend_Layout are as follows: | |
381 | - Automate selection and rendering of layouts when used with the Zend | |
382 | Framework MVC components. | |
383 | - Provide separate scope for layout related variables and content. | |
384 | - Allow configuration, including layout name, layout script resolution | |
385 | (inflection), and layout script path. | |
386 | - Allow disabling layouts, changing layout scripts, and other states; | |
387 | allow these actions from within action controllers and view scripts. | |
388 | - Follow same script resolution rules (inflection) as the | |
389 | ViewRenderer, but allow them to also use different rules. | |
390 | - Allow usage without Zend Framework MVC components. | |
391 | ||
392 | %package Zend_Ldap | |
393 | Summary: Zend_Ldap | |
394 | Group: Development/Languages/PHP | |
395 | URL: http://framework.zend.com/manual/en/zend.ldap.html | |
396 | Requires: %{name} = %{version}-%{release} | |
397 | ||
398 | %description Zend_Ldap | |
399 | Zend_Ldap is a class for performing LDAP operations including but not | |
400 | limited to binding, searching and modifying entries in an LDAP | |
401 | directory. | |
402 | ||
403 | %package Zend_Loader | |
404 | Summary: Zend_Loader | |
405 | Group: Development/Languages/PHP | |
406 | URL: http://framework.zend.com/manual/en/zend.loader.html | |
407 | Requires: %{name} = %{version}-%{release} | |
408 | ||
409 | %description Zend_Loader | |
410 | The Zend_Loader class includes methods to help you load files | |
411 | dynamically. | |
412 | ||
413 | %package Zend_Locale | |
414 | Summary: Zend_Locale | |
415 | Group: Development/Languages/PHP | |
416 | URL: http://framework.zend.com/manual/en/zend.locale.html | |
417 | Requires: %{name} = %{version}-%{release} | |
418 | ||
419 | %description Zend_Locale | |
420 | Zend_Locale is the Framework's answer to the question, "How can the | |
421 | same application be used around the whole world?". This component is | |
422 | the foundation of Zend_Date, Zend_Translate, and others. It provides: | |
423 | - access to CLDR, an international data repository for I18N issues, | |
424 | for all framework classes | |
425 | - localizing of numbers | |
426 | - normalizing of dates, times and numbers. | |
427 | ||
428 | %package Zend_Log | |
429 | Summary: Zend_Log | |
430 | Group: Development/Languages/PHP | |
431 | URL: http://framework.zend.com/manual/en/zend.log.html | |
432 | Requires: %{name} = %{version}-%{release} | |
433 | ||
434 | %description Zend_Log | |
435 | Zend_Log is a component for general purpose logging. It supports | |
436 | multiple log backends, formatting messages sent to the log, and | |
437 | filtering messages from being logged. These functions are divided into | |
438 | the following objects: | |
439 | - A Log (instance of Zend_Log) is the object that your application | |
440 | uses the most. You can have as many Log objects as you like; they do | |
441 | not interact. A Log object must contain at least one Writer, and can | |
442 | optionally contain one or more Filters. | |
443 | - A Writer (inherits from Zend_Log_Writer_Abstract) is responsible for | |
444 | saving data to storage. | |
445 | - A Filter (implements Zend_Log_Filter_Interface) blocks log data from | |
446 | being saved. A filter may be applied to an individual Writer, or to a | |
447 | Log where it is applied before all Writers. In either case, filters | |
448 | may be chained. | |
449 | - A Formatter (implements Zend_Log_Formatter_Interface) can format the | |
450 | log data before it is written by a Writer. Each Writer has exactly one | |
451 | Formatter. | |
452 | ||
453 | %package Zend_Mail | |
454 | Summary: Zend_Mail | |
455 | Group: Development/Languages/PHP | |
456 | URL: http://framework.zend.com/manual/en/zend.mail.html | |
457 | Requires: %{name} = %{version}-%{release} | |
458 | ||
459 | %description Zend_Mail | |
460 | Zend_Mail provides generalized functionality to compose and send both | |
461 | text and MIME-compliant multipart e-mail messages. Mail can be sent | |
462 | with Zend_Mail via the default Zend_Mail_Transport_Sendmail transport | |
463 | or via Zend_Mail_Transport_Smtp. | |
464 | ||
465 | %package Zend_Measure | |
466 | Summary: Zend_Measure | |
467 | Group: Development/Languages/PHP | |
468 | URL: http://framework.zend.com/manual/en/zend.measure.html | |
469 | Requires: %{name} = %{version}-%{release} | |
470 | ||
471 | %description Zend_Measure | |
472 | Zend_Measure component provide a generic and easy way for working with | |
473 | measurements. Using Zend_Measure_* classes, you can convert | |
474 | measurements into different units of the same type. They can be added, | |
475 | subtracted and compared against each other. From a given input made in | |
476 | the user's native language, the unit of measurement can be | |
477 | automatically extracted. Numerous units of measurement are supported. | |
478 | ||
479 | %package Zend_Memory | |
480 | Summary: Zend_Memory | |
481 | Group: Development/Languages/PHP | |
482 | URL: http://framework.zend.com/manual/en/zend.memory.html | |
483 | Requires: %{name} = %{version}-%{release} | |
484 | ||
485 | %description Zend_Memory | |
486 | The Zend_Memory component is intended to manage data in an environment | |
487 | with limited memory. Memory objects (memory containers) are generated | |
488 | by memory manager by request and transparently swapped/loaded when | |
489 | it's necessary. For example, if creating or loading a managed object | |
490 | would cause the total memory usage to exceed the limit you specify, | |
491 | some managed objects are copied to cache storage outside of memory. In | |
492 | this way, the total memory used by managed objects does not exceed the | |
493 | limit you need to enforce. | |
494 | ||
495 | %package Zend_Mime | |
496 | Summary: Zend_Mime | |
497 | Group: Development/Languages/PHP | |
498 | URL: http://framework.zend.com/manual/en/zend.mime.html | |
499 | Requires: %{name} = %{version}-%{release} | |
500 | ||
501 | %description Zend_Mime | |
502 | Zend_Mime is a support class for handling multipart MIME messages. | |
503 | ||
504 | %package Zend_OpenId | |
505 | Summary: Zend_OpenId | |
506 | Group: Development/Languages/PHP | |
507 | URL: http://framework.zend.com/manual/en/zend.openid.html | |
508 | Requires: %{name} = %{version}-%{release} | |
509 | ||
510 | %description Zend_OpenId | |
511 | Zend_OpenId is a Zend Framework component that provides a simple API | |
512 | for building OpenID-enabled sites and identity providers. | |
513 | ||
514 | %package Zend_Paginator | |
515 | Summary: Zend_Paginator | |
516 | Group: Development/Languages/PHP | |
517 | URL: http://framework.zend.com/manual/en/zend.paginator.html | |
518 | Requires: %{name} = %{version}-%{release} | |
519 | ||
520 | %description Zend_Paginator | |
521 | Zend_Paginator is a flexible component for paginating collections of | |
522 | data and presenting that data to users. | |
523 | ||
524 | The primary design goals of Zend_Paginator are as follows: | |
525 | - Paginate arbitrary data, not just relational databases | |
526 | - Fetch only the results that need to be displayed | |
527 | - Do not force users to adhere to only one way of displaying data or | |
528 | rendering pagination controls | |
529 | - Loosely couple Zend_Paginator to other Zend Framework components so | |
530 | that users who wish to use it independently of Zend_View, Zend_Db, | |
531 | etc. can do so. | |
532 | ||
533 | %package Zend_Pdf | |
534 | Summary: Zend_Pdf | |
535 | Group: Development/Languages/PHP | |
536 | URL: http://framework.zend.com/manual/en/zend.pdf.html | |
537 | Requires: %{name} = %{version}-%{release} | |
538 | ||
539 | %description Zend_Pdf | |
540 | Zend_Pdf module is a PDF (Portable Document Format) manipulation | |
541 | engine. It can load existing documents, create new, modify and save | |
542 | modified documents. Thus it can help application dynamically prepare | |
543 | documents in a PDF by modifying existing template or generating | |
544 | document from a scratch. | |
545 | ||
546 | Zend_Pdf module supports the following features: | |
547 | - Create new document or load existing one (PDF V1.4 (Acrobat 5) | |
548 | documents are supported for loading now). | |
549 | - Retrieving specified revision of the document. | |
550 | - Manipulate pages within document. Changing page order, adding new | |
551 | pages, removing pages from a document. | |
552 | - Different drawing primitives (lines, rectangles, polygons, circles, | |
553 | ellipses and sectors). | |
554 | - Text drawing using any of the 14 standard (built-in) fonts or your | |
555 | own custom TrueType fonts. | |
556 | - Rotations. | |
557 | - Image drawing (JPG, PNG [Up to 8bit per channel+Alpha] and TIFF | |
558 | images are supported). | |
559 | - Incremental PDF file update. | |
560 | ||
561 | %package Zend_Registry | |
562 | Summary: Zend_Registry | |
563 | Group: Development/Languages/PHP | |
564 | URL: http://framework.zend.com/manual/en/zend.registry.html | |
565 | Requires: %{name} = %{version}-%{release} | |
566 | ||
567 | %description Zend_Registry | |
568 | The registry is a container for storing objects and values in the | |
569 | application space. By storing the value in the registry, the same | |
570 | object is always available throughout your application. This mechanism | |
571 | is an alternative to using global storage. | |
572 | ||
573 | %package Zend_Rest | |
574 | Summary: Zend_Rest | |
575 | Group: Development/Languages/PHP | |
576 | URL: http://framework.zend.com/manual/en/zend.rest.html | |
577 | Requires: %{name} = %{version}-%{release} | |
578 | ||
579 | %description Zend_Rest | |
580 | REST Web Services use service-specific XML formats. These ad-hoc | |
581 | standards mean that the manner for accessing a REST web service is | |
582 | different for each service. REST web services typically use URL | |
583 | parameters (GET data) or path information for requesting data and POST | |
584 | data for sending data. Zend_Rest component provides: | |
585 | - capabilities to access REST web services | |
586 | - capabilities to expose APIs as REST services | |
587 | ||
588 | %package Zend_Search_Lucene | |
589 | Summary: Zend_Search_Lucene | |
590 | Group: Development/Languages/PHP | |
591 | URL: http://framework.zend.com/manual/en/zend.search.lucene.html | |
592 | Requires: %{name} = %{version}-%{release} | |
593 | ||
594 | %description Zend_Search_Lucene | |
595 | Zend_Search_Lucene is a general purpose text search engine. Since it | |
596 | stores its index on the filesystem and does not require a database | |
597 | server, it can add search capabilities to almost any PHP-driven | |
598 | website. | |
599 | ||
600 | Zend_Search_Lucene supports the following features: | |
601 | - Ranked searching - best results returned first | |
602 | - Many powerful query types: phrase queries, wildcard queries, | |
603 | proximity queries, range queries and more | |
604 | - Search by specific field (e.g., title, author, contents) | |
605 | ||
606 | %package Zend_Server_Reflection | |
607 | Summary: Zend_Server_Reflection | |
608 | Group: Development/Languages/PHP | |
609 | URL: http://framework.zend.com/manual/en/zend.server.reflection.html | |
610 | Requires: %{name} = %{version}-%{release} | |
611 | ||
612 | %description Zend_Server_Reflection | |
613 | Zend_Server_Reflection provides a standard mechanism for performing | |
614 | function and class introspection for use with server classes. It is | |
615 | based on Reflection API, and extends it to provide methods for | |
616 | retrieving parameter and return value types and descriptions, a full | |
617 | list of function and method prototypes (i.e., all possible valid | |
618 | calling combinations), and function/method descriptions. | |
619 | ||
620 | %package Zend_Service_Akismet | |
621 | Summary: Zend_Service_Akismet | |
622 | Group: Development/Languages/PHP | |
623 | URL: http://framework.zend.com/manual/en/zend.service.akismet.html | |
624 | Requires: %{name} = %{version}-%{release} | |
625 | ||
626 | %description Zend_Service_Akismet | |
627 | Zend_Service_Akismet provides a client for the Akismet API. The | |
628 | Akismet service is used to determine if incoming data is potentially | |
629 | spam; it also exposes methods for submitting data as known spam or as | |
630 | false positives (ham). Originally intended to help categorize and | |
631 | identify spam for Wordpress, it can be used for any type of data. | |
632 | ||
633 | Akismet requires an API key for usage. You may get one for signing up | |
634 | for a WordPress.com account. You do not need to activate a blog; | |
635 | simply acquiring the account will provide you with the API key. | |
636 | ||
637 | Additionally, Akismet requires that all requests contain a URL to the | |
638 | resource for which data is being filtered, and, because of Akismet's | |
639 | origins in WordPress, this resource is called the blog url. This value | |
640 | should be passed as the second argument to the constructor, but may be | |
641 | reset at any time using the setBlogUrl() accessor, or overridden by | |
642 | specifying a 'blog' key in the various method calls. | |
643 | ||
644 | %package Zend_Service_Amazon | |
645 | Summary: Zend_Service_Amazon | |
646 | Group: Development/Languages/PHP | |
647 | URL: http://framework.zend.com/manual/en/zend.service.amazon.html | |
648 | Requires: %{name} = %{version}-%{release} | |
649 | ||
650 | %description Zend_Service_Amazon | |
651 | Zend_Service_Amazon is a simple API for using Amazon web services. | |
652 | Zend_Service_Amazon has two APIs: a more traditional one that follows | |
653 | Amazon's own API, and a simpler "Query API" for constructing even | |
654 | complex search queries easily. | |
655 | ||
656 | Zend_Service_Amazon enables developers to retrieve information | |
657 | appearing throughout Amazon.com web sites directly through the Amazon | |
658 | Web Services API. | |
659 | ||
660 | %package Zend_Service_Audioscrobbler | |
661 | Summary: Zend_Service_Audioscrobbler | |
662 | Group: Development/Languages/PHP | |
663 | URL: http://framework.zend.com/manual/en/zend.service.audioscrobbler.html | |
664 | Requires: %{name} = %{version}-%{release} | |
665 | ||
666 | %description Zend_Service_Audioscrobbler | |
667 | Zend_Service_Audioscrobbler is a simple API for using the | |
668 | Audioscrobbler REST Web Service. The Audioscrobbler Web Service | |
669 | provides access to its database of Users, Artists, Albums, Tracks, | |
670 | Tags, Groups, and Forums. | |
671 | ||
672 | %package Zend_Service_Delicious | |
673 | Summary: Zend_Service_Delicious | |
674 | Group: Development/Languages/PHP | |
675 | URL: http://framework.zend.com/manual/en/zend.service.delicious.html | |
676 | Requires: %{name} = %{version}-%{release} | |
677 | ||
678 | %description Zend_Service_Delicious | |
679 | Zend_Service_Delicious is simple API for using del.icio.us XML and | |
680 | JSON web services. This component gives you read-write access to posts | |
681 | at del.icio.us if you provide credentials. It also allows read-only | |
682 | access to public data of all users. | |
683 | ||
684 | %package Zend_Service_Flickr | |
685 | Summary: Zend_Service_Flickr | |
686 | Group: Development/Languages/PHP | |
687 | URL: http://framework.zend.com/manual/en/zend.service.delicious.html | |
688 | Requires: %{name} = %{version}-%{release} | |
689 | ||
690 | %description Zend_Service_Flickr | |
691 | Zend_Service_Flickr is a simple API for using the Flickr REST Web | |
692 | Service. In order to use the Flickr web services, you must have an API | |
693 | key. To obtain a key, visit the Flickr API Documentation | |
694 | (http://www.flickr.com/services/api/). | |
695 | ||
696 | %package Zend_Service_Nirvanix | |
697 | Summary: Zend_Service_Nirvanix | |
698 | Group: Development/Languages/PHP | |
699 | URL: http://framework.zend.com/manual/en/zend.service.nirvanix.html | |
700 | Requires: %{name} = %{version}-%{release} | |
701 | ||
702 | %description Zend_Service_Nirvanix | |
703 | Nirvanix provides an Internet Media File System (IMFS), an Internet | |
704 | storage service that allows applications to upload, store and organize | |
705 | files and subsequently access them using a standard Web Services | |
706 | interface. An IMFS is distributed clustered file system, accessed over | |
707 | the Internet, and optimized for dealing with media files (audio, | |
708 | video, etc). The goal of an IMFS is to provide massive scalability to | |
709 | deal with the challenges of media storage growth, with guaranteed | |
710 | access and availability regardless of time and location. Finally, an | |
711 | IMFS gives applications the ability to access data securely, without | |
712 | the large fixed costs associated with acquiring and maintaining | |
713 | physical storage assets. | |
714 | ||
715 | Before you can get started with Zend_Service_Nirvanix, you must first | |
716 | register for an account (https://www.nirvanix.com/signUpSingle.aspx). | |
717 | After registering, you will receive a Username, Password, and | |
718 | Application Key. All three are required to use Zend_Service_Nirvanix. | |
719 | ||
720 | %package Zend_Service_ReCaptcha | |
721 | Summary: Zend_Service_ReCaptcha | |
722 | Group: Development/Languages/PHP | |
723 | URL: http://framework.zend.com/manual/en/zend.service.recaptcha.html | |
724 | Requires: %{name} = %{version}-%{release} | |
725 | ||
726 | %description Zend_Service_ReCaptcha | |
727 | Zend_Service_ReCaptcha provides a client for the reCAPTCHA Web | |
728 | Service. Per the reCAPTCHA site, "reCAPTCHA is a free CAPTCHA service | |
729 | that helps to digitize books." Each reCAPTCHA requires the user to | |
730 | input two words, the first of which is the actual captcha, and the | |
731 | second of which is a word from some scanned text that Optical | |
732 | Character Recognition (OCR) software has been unable to identifiy. The | |
733 | assumption is that if a user correctly provides the first word, the | |
734 | second is likely correctly entered as well, and can be used to improve | |
735 | OCR software for digitizing books. | |
736 | ||
737 | In order to use the reCAPTCHA service, you will need to sign up for an | |
738 | account (http://recaptcha.net/whyrecaptcha.html) and register one or | |
739 | more domains with the service in order to generate public and private | |
740 | keys. | |
741 | ||
742 | %package Zend_Service_Simpy | |
743 | Summary: Zend_Service_Simpy | |
744 | Group: Development/Languages/PHP | |
745 | URL: http://framework.zend.com/manual/en/zend.service.simpy.html | |
746 | Requires: %{name} = %{version}-%{release} | |
747 | ||
748 | %description Zend_Service_Simpy | |
749 | Zend_Service_Simpy is a lightweight wrapper for the free REST API | |
750 | available for the Simpy social bookmarking service. | |
751 | ||
752 | In order to use Zend_Service_Simpy, you should already have a Simpy | |
753 | account. To get an account, visit the Simpy web site | |
754 | (http://simpy.com/). | |
755 | ||
756 | %package Zend_Service_SlideShare | |
757 | Summary: Zend_Service_SlideShare | |
758 | Group: Development/Languages/PHP | |
759 | URL: http://framework.zend.com/manual/en/zend.service.slideshare.html | |
760 | Requires: %{name} = %{version}-%{release} | |
761 | ||
762 | %description Zend_Service_SlideShare | |
763 | The Zend_Service_SlideShare component is used to interact with the | |
764 | slideshare.net web services for hosting slide shows online. With this | |
765 | component, you can embed slide shows which are hosted on this web site | |
766 | within a web site and even upload new slide shows to your account. | |
767 | ||
768 | In order to use the Zend_Service_SlideShare component you must first | |
769 | create an account on the slideshare.net servers in order to receive an | |
770 | API key, username, password and shared secret value -- all of which | |
771 | are needed in order to use the Zend_Service_SlideShare component. | |
772 | ||
773 | %package Zend_Service_StrikeIron | |
774 | Summary: Zend_Service_StrikeIron | |
775 | Group: Development/Languages/PHP | |
776 | URL: http://framework.zend.com/manual/en/zend.service.strikeiron.html | |
777 | Requires: %{name} = %{version}-%{release} | |
778 | ||
779 | %description Zend_Service_StrikeIron | |
780 | Zend_Service_StrikeIron provides a client to StrikeIron web services. | |
781 | ||
782 | The Zend_Service_StrikeIron component provides: | |
783 | - A single point for configuring your StrikeIron authentication | |
784 | credentials that can be used across many StrikeIron services. | |
785 | - A standard way of retrieving your StrikeIron subscription | |
786 | information such as license status and the number of hits remaining to | |
787 | a service. | |
788 | - The ability to use any StrikeIron service from its WSDL without | |
789 | creating a PHP wrapper class, and the option of creating a wrapper for | |
790 | a more convenient interface. | |
791 | - Wrappers for three popular StrikeIron services. | |
792 | ||
793 | Before you can get started with Zend_Service_StrikeIron, you must | |
794 | first register (http://strikeiron.com/Register.aspx) for a StrikeIron | |
795 | developer account. After registering, you will receive a StrikeIron | |
796 | username and password. These will be used when connecting to | |
797 | StrikeIron using Zend_Service_StrikeIron. You will also need to sign | |
798 | up (http://www.strikeiron.com/ProductDetail.aspx?p=257) for | |
799 | StrikeIron's Super Data Pack Web Service. Both registration steps are | |
800 | free and can be done relatively quickly through the StrikeIron | |
801 | website. | |
802 | ||
803 | %package Zend_Service_Technorati | |
804 | Summary: Zend_Service_Technorati | |
805 | Group: Development/Languages/PHP | |
806 | URL: http://framework.zend.com/manual/en/zend.service.technorati.html | |
807 | Requires: %{name} = %{version}-%{release} | |
808 | ||
809 | %description Zend_Service_Technorati | |
810 | Zend_Service_Technorati provides an easy, intuitive and | |
811 | object-oriented interface for using the Technorati API. It provides | |
812 | access to all available Technorati API queries and returns the | |
813 | original XML response as a friendly PHP object. | |
814 | ||
815 | Technorati requires a valid API key for usage. To get your own API Key | |
816 | you first need to create a new Technorati account | |
817 | (http://technorati.com/signup/), then visit the API Key section | |
818 | (http://technorati.com/developers/apikey.html). | |
819 | ||
820 | %package Zend_Service_Yahoo | |
821 | Summary: Zend_Service_Yahoo | |
822 | Group: Development/Languages/PHP | |
823 | URL: http://framework.zend.com/manual/en/zend.service.yahoo.html | |
824 | Requires: %{name} = %{version}-%{release} | |
825 | ||
826 | %description Zend_Service_Yahoo | |
827 | Zend_Service_Yahoo is a simple API for using many of the Yahoo! REST | |
828 | APIs. Zend_Service_Yahoo allows you to search Yahoo! Web search, | |
829 | Yahoo! News, Yahoo! Local, Yahoo! Images. In order to use the Yahoo! | |
830 | REST API, you must have a Yahoo! Application ID. To obtain an | |
831 | Application ID, please complete and submit the Application ID Request | |
832 | Form (http://developer.yahoo.com/wsregapp/). | |
833 | ||
834 | %package Zend_Session | |
835 | Summary: Zend_Session | |
836 | Group: Development/Languages/PHP | |
837 | URL: http://framework.zend.com/manual/en/zend.session.html | |
838 | Requires: %{name} = %{version}-%{release} | |
839 | ||
840 | %description Zend_Session | |
841 | Zend_Session helps manage and preserve session data across multiple | |
842 | page requests by the same client. Zend_Session component: | |
843 | - provides an object-oriented interface to access session data | |
844 | - provides optional security features to help protect against session | |
845 | hijacking | |
846 | - supports namespaced access to the PHP session for interoperability. | |
847 | ||
848 | %package Zend_Soap | |
849 | Summary: Zend_Soap | |
850 | Group: Development/Languages/PHP | |
851 | URL: http://framework.zend.com/manual/en/zend.soap.html | |
852 | Requires: %{name} = %{version}-%{release} | |
853 | ||
854 | %description Zend_Soap | |
855 | Zend_Soap component is intended to simplify Web Services development | |
856 | for PHP programmers. | |
857 | ||
858 | %package Zend_Text | |
859 | Summary: Zend_Text | |
860 | Group: Development/Languages/PHP | |
861 | URL: http://framework.zend.com/manual/en/zend.text.html | |
862 | Requires: %{name} = %{version}-%{release} | |
863 | ||
864 | %description Zend_Text | |
865 | Zend_Text is a component which enables developers to create a so | |
866 | called FIGlet text. A FIGlet text is a string, which is represented as | |
867 | ASCII art. FIGlets use a special font format, called FLT (FigLet | |
868 | Font). | |
869 | ||
870 | %package Zend_Test | |
871 | Summary: Zend_Test | |
872 | Group: Development/Languages/PHP | |
873 | URL: http://framework.zend.com/manual/en/zend.test.html | |
874 | Requires: %{name} = %{version}-%{release} | |
875 | ||
876 | %description Zend_Test | |
877 | Zend_Test provides tools to facilitate unit testing of your Zend | |
878 | Framework applications. | |
879 | ||
880 | %package Zend_Translate | |
881 | Summary: Zend_Translate | |
882 | Group: Development/Languages/PHP | |
883 | URL: http://framework.zend.com/manual/en/zend.translate.html | |
884 | Requires: %{name} = %{version}-%{release} | |
885 | ||
886 | %description Zend_Translate | |
887 | Zend_Translate is the Zend Framework's solution for multilingual | |
888 | applications. | |
889 | ||
890 | The benefits of Zend_Translate are: | |
891 | - Supports multiple source formats: Zend_Translate supports several | |
892 | source formats, including those supported by PHP, and other formats | |
893 | including TMX and CSV files. | |
894 | - Thread-safe gettext: The gettext reader of Zend_Translate is | |
895 | thread-safe. There are no problems using it in multi-threaded | |
896 | environments. | |
897 | - Easy and generic API: The API of Zend_Translate is very simple and | |
898 | requires only a handful of functions. So it's easy to learn and easy | |
899 | to maintain. All source formats are handled the same way, so if the | |
900 | format of your source files change from Gettext to TMX, you only need | |
901 | to change one line of code to specify the storage adapter. | |
902 | - Detection of the user's standard language: The preferred language of | |
903 | the user accessing the site can be detected and used by | |
904 | Zend_Translate. | |
905 | - Automatic source detection: Zend_Translate is capable of detecting | |
906 | and integrating multiple source files and additionally detect the | |
907 | locale to be used depending on directory or filenames. | |
908 | ||
909 | %package Zend_Uri | |
910 | Summary: Zend_Uri | |
911 | Group: Development/Languages/PHP | |
912 | URL: http://framework.zend.com/manual/en/zend.uri.html | |
913 | Requires: %{name} = %{version}-%{release} | |
914 | ||
915 | %description Zend_Uri | |
916 | Zend_Uri is a component that aids in manipulating and validating | |
917 | Uniform Resource Identifiers (URIs). Zend_Uri exists primarily to | |
918 | service other components such as Zend_Http_Client but is also useful | |
919 | as a standalone utility. | |
920 | ||
921 | %package Zend_Validate | |
922 | Summary: Zend_Validate | |
923 | Group: Development/Languages/PHP | |
924 | URL: http://framework.zend.com/manual/en/zend.validate.html | |
925 | Requires: %{name} = %{version}-%{release} | |
926 | ||
927 | %description Zend_Validate | |
928 | The Zend_Validate component provides a set of commonly needed | |
929 | validators. It also provides a simple validator chaining mechanism by | |
930 | which multiple validators may be applied to a single datum in a | |
931 | user-defined order. | |
932 | ||
933 | %package Zend_Version | |
934 | Summary: Zend_Version | |
935 | Group: Development/Languages/PHP | |
936 | URL: http://framework.zend.com/manual/en/zend.version.html | |
937 | Requires: %{name} = %{version}-%{release} | |
938 | ||
939 | %description Zend_Version | |
940 | Zend_Version component delivers current version number of Zend | |
941 | Framework. | |
942 | ||
943 | %package Zend_View | |
944 | Summary: Zend_View | |
945 | Group: Development/Languages/PHP | |
946 | URL: http://framework.zend.com/manual/en/zend.view.html | |
947 | Requires: %{name} = %{version}-%{release} | |
948 | ||
949 | %description Zend_View | |
950 | Zend_View is a class for working with the "view" portion of the | |
951 | model-view-controller pattern. That is, it exists to help keep the | |
952 | view script separate from the model and controller scripts. It | |
953 | provides a system of helpers, output filters, and variable escaping. | |
954 | Zend_View is template system agnostic; you may use PHP as your | |
955 | template language, or create instances of other template systems and | |
956 | manipulate them within your view script. Essentially, using Zend_View | |
957 | happens in two major steps: 1. Your controller script creates an | |
958 | instance of Zend_View and assigns variables to that instance. 2. The | |
959 | controller tells the Zend_View to render a particular view, thereby | |
960 | handing control over the view script, which generates the view output. | |
961 | ||
962 | %package Zend_Wildfire | |
963 | Summary: Zend_Wildfire | |
964 | Group: Development/Languages/PHP | |
965 | URL: http://framework.zend.com/manual/en/zend.wildfire.html | |
966 | Requires: %{name} = %{version}-%{release} | |
967 | ||
968 | %description Zend_Wildfire | |
969 | Zend_Wildfire is a component that facilitates communication between | |
970 | PHP code and Wildfire client components. The purpose of the Wildfire | |
971 | Project is to develop standardized communication channels between a | |
972 | large variety of components and a dynamic and scriptable plugin | |
973 | architecture. At this time the primary focus is to provide a system to | |
974 | allow server-side PHP code to inject logging messages into the Firebug | |
975 | Console (http://getfirebug.com/). | |
976 | ||
977 | %package Zend_XmlRpc | |
978 | Summary: Zend_XmlRpc | |
979 | Group: Development/Languages/PHP | |
980 | URL: http://framework.zend.com/manual/en/zend.xmlrpc.html | |
981 | Requires: %{name} = %{version}-%{release} | |
982 | ||
983 | %description Zend_XmlRpc | |
984 | From its home page (http://www.xmlrpc.com/), XML-RPC is described as a | |
985 | "...remote procedure calling using HTTP as the transport and XML as | |
986 | the encoding. XML-RPC is designed to be as simple as possible, while | |
987 | allowing complex data structures to be transmitted, processed and | |
988 | returned". The Zend Framework provides support for both consuming | |
989 | remote XML-RPC services and building new XML-RPC servers. | |
990 | ||
6e96c14e ER |
991 | %package demos |
992 | Summary: Demos for Zend Framework | |
661af80f | 993 | Summary(pl.UTF-8): Programy demonstracyjne dla szkieletu Zend Framework |
6e96c14e ER |
994 | Group: Documentation |
995 | ||
996 | %description demos | |
997 | Demos for Zend Framework. | |
998 | ||
661af80f JB |
999 | %description demos -l pl.UTF-8 |
1000 | Programy demonstracyjne dla szkieletu Zend Framework. | |
1001 | ||
366e32c5 ER |
1002 | %prep |
1003 | %setup -q | |
1004 | ||
1005 | %install | |
1006 | rm -rf $RPM_BUILD_ROOT | |
9d1d6b31 | 1007 | install -d $RPM_BUILD_ROOT{%{_examplesdir}/%{name}-%{version},%{php_pear_dir}} |
366e32c5 ER |
1008 | cp -a demos/Zend/* $RPM_BUILD_ROOT%{_examplesdir}/%{name}-%{version} |
1009 | ||
9d1d6b31 ER |
1010 | # library should be in include_path if used, so we use already defined %{php_pear_dir} |
1011 | cp -a library/* $RPM_BUILD_ROOT%{php_pear_dir} | |
366e32c5 | 1012 | |
366e32c5 ER |
1013 | %clean |
1014 | rm -rf $RPM_BUILD_ROOT | |
1015 | ||
1016 | %files | |
1017 | %defattr(644,root,root,755) | |
b56139b1 | 1018 | %doc LICENSE.txt README.txt |
e71cf32a | 1019 | %dir %{php_pear_dir}/Zend |
1020 | %dir %{php_pear_dir}/Zend/Console | |
1021 | %dir %{php_pear_dir}/Zend/Search | |
1022 | ||
1023 | %dir %{php_pear_dir}/Zend/Server | |
1024 | %{php_pear_dir}/Zend/Server/Abstract.php | |
1025 | %{php_pear_dir}/Zend/Server/Exception.php | |
1026 | %{php_pear_dir}/Zend/Server/Interface.php | |
1027 | ||
1028 | %dir %{php_pear_dir}/Zend/Service | |
1029 | %{php_pear_dir}/Zend/Service/Abstract.php | |
1030 | %{php_pear_dir}/Zend/Service/Exception.php | |
1031 | ||
1032 | %dir %{php_pear_dir}/Zend/Request | |
1033 | %{php_pear_dir}/Zend/Request/Interface.php | |
1034 | ||
1035 | %{php_pear_dir}/Zend/TimeSync | |
1036 | %{php_pear_dir}/Zend/TimeSync.php | |
1037 | ||
1038 | %files Zend_Acl | |
1039 | %defattr(644,root,root,755) | |
1040 | %{php_pear_dir}/Zend/Acl | |
1041 | %{php_pear_dir}/Zend/Acl.php | |
1042 | ||
1043 | %files Zend_Auth | |
1044 | %defattr(644,root,root,755) | |
1045 | %{php_pear_dir}/Zend/Auth | |
1046 | %{php_pear_dir}/Zend/Auth.php | |
1047 | ||
1048 | %files Zend_Cache | |
1049 | %defattr(644,root,root,755) | |
1050 | %{php_pear_dir}/Zend/Cache | |
1051 | %{php_pear_dir}/Zend/Cache.php | |
1052 | ||
1053 | %files Zend_Captcha | |
1054 | %defattr(644,root,root,755) | |
1055 | %{php_pear_dir}/Zend/Captcha | |
1056 | ||
1057 | %files Zend_Config | |
1058 | %defattr(644,root,root,755) | |
1059 | %{php_pear_dir}/Zend/Config | |
1060 | %{php_pear_dir}/Zend/Config.php | |
1061 | ||
1062 | %files Zend_Console_Getopt | |
1063 | %defattr(644,root,root,755) | |
1064 | %{php_pear_dir}/Zend/Console/Getopt | |
1065 | %{php_pear_dir}/Zend/Console/Getopt.php | |
1066 | ||
1067 | %files Zend_Controller | |
1068 | %defattr(644,root,root,755) | |
1069 | %{php_pear_dir}/Zend/Controller | |
1070 | ||
1071 | %files Zend_Currency | |
1072 | %defattr(644,root,root,755) | |
1073 | %{php_pear_dir}/Zend/Currency | |
1074 | %{php_pear_dir}/Zend/Currency.php | |
1075 | ||
1076 | %files Zend_Date | |
1077 | %defattr(644,root,root,755) | |
1078 | %{php_pear_dir}/Zend/Date | |
1079 | %{php_pear_dir}/Zend/Date.php | |
1080 | ||
1081 | %files Zend_Db | |
1082 | %defattr(644,root,root,755) | |
1083 | %{php_pear_dir}/Zend/Db | |
1084 | %{php_pear_dir}/Zend/Db.php | |
1085 | ||
1086 | %files Zend_Debug | |
1087 | %defattr(644,root,root,755) | |
1088 | %{php_pear_dir}/Zend/Debug.php | |
1089 | ||
1090 | %files Zend_Dojo | |
1091 | %defattr(644,root,root,755) | |
1092 | %{php_pear_dir}/Zend/Dojo | |
1093 | %{php_pear_dir}/Zend/Dojo.php | |
1094 | ||
1095 | %files Zend_Dom | |
1096 | %defattr(644,root,root,755) | |
1097 | %{php_pear_dir}/Zend/Dom | |
1098 | ||
1099 | %files Zend_Exception | |
1100 | %defattr(644,root,root,755) | |
1101 | %{php_pear_dir}/Zend/Exception.php | |
1102 | ||
1103 | %files Zend_Feed | |
1104 | %defattr(644,root,root,755) | |
1105 | %{php_pear_dir}/Zend/Feed | |
1106 | %{php_pear_dir}/Zend/Feed.php | |
1107 | ||
1108 | %files Zend_File | |
1109 | %defattr(644,root,root,755) | |
1110 | %{php_pear_dir}/Zend/File | |
1111 | ||
1112 | %files Zend_Filter | |
1113 | %defattr(644,root,root,755) | |
1114 | %{php_pear_dir}/Zend/Filter | |
1115 | %{php_pear_dir}/Zend/Filter.php | |
1116 | #??? | |
1117 | %exclude %{php_pear_dir}/Zend/Filter/Input.php | |
1118 | ||
1119 | %files Zend_Filter_Input | |
1120 | %defattr(644,root,root,755) | |
1121 | %{php_pear_dir}/Zend/Filter/Input.php | |
1122 | ||
1123 | %files Zend_Form | |
1124 | %defattr(644,root,root,755) | |
1125 | %{php_pear_dir}/Zend/Form | |
1126 | %{php_pear_dir}/Zend/Form.php | |
1127 | ||
1128 | %files Zend_Gdata | |
1129 | %defattr(644,root,root,755) | |
1130 | %{php_pear_dir}/Zend/Gdata | |
1131 | %{php_pear_dir}/Zend/Gdata.php | |
1132 | ||
1133 | %files Zend_Http | |
1134 | %defattr(644,root,root,755) | |
1135 | %{php_pear_dir}/Zend/Http | |
1136 | ||
1137 | %files Zend_InfoCard | |
1138 | %defattr(644,root,root,755) | |
1139 | %{php_pear_dir}/Zend/InfoCard | |
1140 | %{php_pear_dir}/Zend/InfoCard.php | |
1141 | ||
1142 | %files Zend_Json | |
1143 | %defattr(644,root,root,755) | |
1144 | %{php_pear_dir}/Zend/Json | |
1145 | %{php_pear_dir}/Zend/Json.php | |
1146 | ||
1147 | %files Zend_Layout | |
1148 | %defattr(644,root,root,755) | |
1149 | %{php_pear_dir}/Zend/Layout | |
1150 | %{php_pear_dir}/Zend/Layout.php | |
1151 | ||
1152 | %files Zend_Ldap | |
1153 | %defattr(644,root,root,755) | |
1154 | %{php_pear_dir}/Zend/Ldap | |
1155 | %{php_pear_dir}/Zend/Ldap.php | |
1156 | ||
1157 | %files Zend_Loader | |
1158 | %defattr(644,root,root,755) | |
1159 | %{php_pear_dir}/Zend/Loader | |
1160 | %{php_pear_dir}/Zend/Loader.php | |
1161 | ||
1162 | %files Zend_Locale | |
1163 | %defattr(644,root,root,755) | |
1164 | %{php_pear_dir}/Zend/Locale | |
1165 | %{php_pear_dir}/Zend/Locale.php | |
1166 | ||
1167 | %files Zend_Log | |
1168 | %defattr(644,root,root,755) | |
1169 | %{php_pear_dir}/Zend/Log | |
1170 | %{php_pear_dir}/Zend/Log.php | |
1171 | ||
1172 | %files Zend_Mail | |
1173 | %defattr(644,root,root,755) | |
1174 | %{php_pear_dir}/Zend/Mail | |
1175 | %{php_pear_dir}/Zend/Mail.php | |
1176 | ||
1177 | %files Zend_Measure | |
1178 | %defattr(644,root,root,755) | |
1179 | %{php_pear_dir}/Zend/Measure | |
1180 | ||
1181 | %files Zend_Memory | |
1182 | %defattr(644,root,root,755) | |
1183 | %{php_pear_dir}/Zend/Memory | |
1184 | %{php_pear_dir}/Zend/Memory.php | |
1185 | ||
1186 | %files Zend_Mime | |
1187 | %defattr(644,root,root,755) | |
1188 | %{php_pear_dir}/Zend/Mime | |
1189 | %{php_pear_dir}/Zend/Mime.php | |
1190 | ||
1191 | %files Zend_OpenId | |
1192 | %defattr(644,root,root,755) | |
1193 | %{php_pear_dir}/Zend/OpenId | |
1194 | %{php_pear_dir}/Zend/OpenId.php | |
1195 | ||
1196 | %files Zend_Paginator | |
1197 | %defattr(644,root,root,755) | |
1198 | %{php_pear_dir}/Zend/Paginator | |
1199 | %{php_pear_dir}/Zend/Paginator.php | |
1200 | ||
1201 | %files Zend_Pdf | |
1202 | %defattr(644,root,root,755) | |
1203 | %{php_pear_dir}/Zend/Pdf | |
1204 | %{php_pear_dir}/Zend/Pdf.php | |
1205 | ||
1206 | %files Zend_Registry | |
1207 | %defattr(644,root,root,755) | |
1208 | %{php_pear_dir}/Zend/Registry.php | |
1209 | ||
1210 | %files Zend_Rest | |
1211 | %defattr(644,root,root,755) | |
1212 | %{php_pear_dir}/Zend/Rest | |
1213 | ||
1214 | %files Zend_Search_Lucene | |
1215 | %defattr(644,root,root,755) | |
1216 | %{php_pear_dir}/Zend/Search/Exception.php | |
1217 | %{php_pear_dir}/Zend/Search/Lucene | |
1218 | %{php_pear_dir}/Zend/Search/Lucene.php | |
1219 | ||
1220 | %files Zend_Server_Reflection | |
1221 | %defattr(644,root,root,755) | |
1222 | %{php_pear_dir}/Zend/Server/Reflection | |
1223 | %{php_pear_dir}/Zend/Server/Reflection.php | |
1224 | ||
1225 | %files Zend_Service_Akismet | |
1226 | %defattr(644,root,root,755) | |
1227 | %{php_pear_dir}/Zend/Service/Akismet.php | |
1228 | ||
1229 | %files Zend_Service_Amazon | |
1230 | %defattr(644,root,root,755) | |
1231 | %{php_pear_dir}/Zend/Service/Amazon | |
1232 | %{php_pear_dir}/Zend/Service/Amazon.php | |
1233 | ||
1234 | %files Zend_Service_Audioscrobbler | |
1235 | %defattr(644,root,root,755) | |
1236 | %{php_pear_dir}/Zend/Service/Audioscrobbler.php | |
1237 | ||
1238 | %files Zend_Service_Delicious | |
1239 | %defattr(644,root,root,755) | |
1240 | %{php_pear_dir}/Zend/Service/Delicious | |
1241 | %{php_pear_dir}/Zend/Service/Delicious.php | |
1242 | ||
1243 | %files Zend_Service_Flickr | |
1244 | %defattr(644,root,root,755) | |
1245 | %{php_pear_dir}/Zend/Service/Flickr | |
1246 | %{php_pear_dir}/Zend/Service/Flickr.php | |
1247 | ||
1248 | %files Zend_Service_Nirvanix | |
1249 | %defattr(644,root,root,755) | |
1250 | %{php_pear_dir}/Zend/Service/Nirvanix | |
1251 | %{php_pear_dir}/Zend/Service/Nirvanix.php | |
1252 | ||
1253 | %files Zend_Service_ReCaptcha | |
1254 | %defattr(644,root,root,755) | |
1255 | %{php_pear_dir}/Zend/Service/ReCaptcha | |
1256 | %{php_pear_dir}/Zend/Service/ReCaptcha.php | |
1257 | ||
1258 | %files Zend_Service_Simpy | |
1259 | %defattr(644,root,root,755) | |
1260 | %{php_pear_dir}/Zend/Service/Simpy | |
1261 | %{php_pear_dir}/Zend/Service/Simpy.php | |
1262 | ||
1263 | %files Zend_Service_SlideShare | |
1264 | %defattr(644,root,root,755) | |
1265 | %{php_pear_dir}/Zend/Service/SlideShare | |
1266 | %{php_pear_dir}/Zend/Service/SlideShare.php | |
1267 | ||
1268 | %files Zend_Service_StrikeIron | |
1269 | %defattr(644,root,root,755) | |
1270 | %{php_pear_dir}/Zend/Service/StrikeIron | |
1271 | %{php_pear_dir}/Zend/Service/StrikeIron.php | |
1272 | ||
1273 | %files Zend_Service_Technorati | |
1274 | %defattr(644,root,root,755) | |
1275 | %{php_pear_dir}/Zend/Service/Technorati | |
1276 | %{php_pear_dir}/Zend/Service/Technorati.php | |
1277 | ||
1278 | %files Zend_Service_Yahoo | |
1279 | %defattr(644,root,root,755) | |
1280 | %{php_pear_dir}/Zend/Service/Yahoo | |
1281 | %{php_pear_dir}/Zend/Service/Yahoo.php | |
1282 | ||
1283 | %files Zend_Session | |
1284 | %defattr(644,root,root,755) | |
1285 | %{php_pear_dir}/Zend/Session | |
1286 | %{php_pear_dir}/Zend/Session.php | |
1287 | ||
1288 | %files Zend_Soap | |
1289 | %defattr(644,root,root,755) | |
1290 | %{php_pear_dir}/Zend/Soap | |
1291 | ||
1292 | %files Zend_Text | |
1293 | %defattr(644,root,root,755) | |
1294 | %{php_pear_dir}/Zend/Text | |
1295 | ||
1296 | %files Zend_Test | |
1297 | %defattr(644,root,root,755) | |
1298 | %{php_pear_dir}/Zend/Test | |
1299 | ||
1300 | %files Zend_Translate | |
1301 | %defattr(644,root,root,755) | |
1302 | %{php_pear_dir}/Zend/Translate | |
1303 | %{php_pear_dir}/Zend/Translate.php | |
1304 | ||
1305 | %files Zend_Uri | |
1306 | %defattr(644,root,root,755) | |
1307 | %{php_pear_dir}/Zend/Uri | |
1308 | %{php_pear_dir}/Zend/Uri.php | |
1309 | ||
1310 | %files Zend_Validate | |
1311 | %defattr(644,root,root,755) | |
1312 | %{php_pear_dir}/Zend/Validate | |
1313 | %{php_pear_dir}/Zend/Validate.php | |
1314 | ||
1315 | %files Zend_Version | |
1316 | %defattr(644,root,root,755) | |
1317 | %{php_pear_dir}/Zend/Version.php | |
1318 | ||
1319 | %files Zend_View | |
1320 | %defattr(644,root,root,755) | |
1321 | %{php_pear_dir}/Zend/View | |
1322 | %{php_pear_dir}/Zend/View.php | |
1323 | ||
1324 | %files Zend_Wildfire | |
1325 | %defattr(644,root,root,755) | |
1326 | %{php_pear_dir}/Zend/Wildfire | |
1327 | ||
1328 | %files Zend_XmlRpc | |
1329 | %defattr(644,root,root,755) | |
1330 | %{php_pear_dir}/Zend/XmlRpc | |
9f190b56 | 1331 | |
6e96c14e | 1332 | %files demos |
9f190b56 | 1333 | %defattr(644,root,root,755) |
6e96c14e | 1334 | %{_examplesdir}/%{name}-%{version} |