README.html

   1 <html>
   2 <head>
   3   <meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
   4   <title></title>
   5 </head>
   6
   7 <body>
   8
   9 <div>
  10 <h2>make-srpm program</h2>
  11
  12 <p>Copyright (C) 2008-2010 Sam Liddicott &lt;sam@liddicott.com&gt;</p>
  13
  14 <p></p>
  15
  16 <p>This program is free software; you can redistribute it and/or modify it
  17 under the terms of the GNU General Public License as published by the Free
  18 Software Foundation; either version 3 of the License, or</p>
  19
  20 <p>(at your option) any later version.</p>
  21
  22 <p>This program is distributed in the hope that it will be useful, but WITHOUT
  23 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
  24 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
  25 details.</p>
  26
  27 <p>You should have received a copy of the GNU General Public License along with
  28 this program. If not, see &lt;<a
  29 href="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</a>&gt;.</p>
  30
  31 <p></p>
  32
  33 <p>This documentation is licensed under the </p>
  34
  35 <h2>make-srpm documentation</h2>
  36
  37 <p>Copyright (C) 2008-2010 Sam Liddicott &lt;sam@liddicott.com&gt;</p>
  38
  39 <p>Permission is granted to copy, distribute and/or modify this document under
  40 the terms of the GNU Free Documentation License, Version 1.3 or any later
  41 version published by the Free Software Foundation; with no Invariant Sections,
  42 no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is
  43 included in the section entitled "GNU Free Documentation License".</p>
  44
  45 <h2>Introduction<br>
  46 </h2>
  47
  48 <p>Here are some scripts which I use to produce a src.rpm from a git tree. In
  49 accordance with rpm philosphy, a <em>pristine source</em> tar.gz is produced,
  50 with a series of patches up to the current released. The svn backend is less
  51 developed, as I am not so familiar with svn as I am with git, but it works
  52 enough for my use with the <a target="_blank"
  53 href="http://www.openchange.org/">openchange</a> project.<br>
  54 <br>
  55 The general usage is:<br>
  56 </p>
  57
  58 <blockquote>
  59   <tt>make-srpm [options] project.spec [...]</tt><br>
  60 </blockquote>
  61 and this should be invoked from within or below the git/svn checkout
  62 directory.<br>
  63 <br>
  64 <strong>Note:</strong> make-srpm will cd to the top-level git/svn directory
  65 before working. Multiple .spec files can be specified, and these can be
  66 absolute paths or relative to the current directory (not the top level
  67 directory).<br>
  68 <br>
  69 make-srpm will generate a new .spec file based on the on you provide, and then
  70 use this spec file along with the specified environment it will build the
  71 binary RPMS.<br>
  72 <br>
  73 make-srpm creates a folder called <em>dist-export</em> in the top level git
  74 directory. <br>
  75 <br>
  76 Into this folder it will export the <em>pristine source</em> as specified by
  77 the RELEASE variable, along with any other files in the $EXTRA_SOURCE directory
  78 (relative to the spec file).<br>
  79 <br>
  80 Numbered patches are then produced, starting after the highest patch already in
  81 the spec file.<br>
  82 <br>
  83 <em>dist-export</em> then contains everything required, and the src.rpm is
  84 build using <em>rpmbuild --nodeps</em> <br>
  85
  86
  87 <h2>Options and Macros<br>
  88 </h2>
  89 The operation of make-srpm is generally controlled by shell variables which may
  90 be set explicitly in the environment before calling make-srpm, or specified as
  91 command arguments in makefile fashion; e.g. <br>
  92
  93
  94 <blockquote>
  95   <tt>make-srpm <strong>ORIGIN_PATTERN="*alpha*"</strong> project.spec</tt><br>
  96 </blockquote>
  97
  98 <p>or from within the specfile from specially formed comments.<br>
  99 <br>
 100 The <em>Name:</em> and <em>Version:</em> fields are always extracted and stored
 101 in the environment variables <em>Name</em> and <em>Version</em>.<br>
 102 <br>
 103 The following comments are also searched:<br>
 104 #make-srpm-SOURCE_PATHS:<br>
 105 #make-srpm-ORIGIN:<br>
 106 #make-srpm-ORIGIN_PATTERN:<br>
 107 #make-srpm-RELEASE:<br>
 108 #make-srpm-PATCH_LEVEL:<br>
 109 #makesrpm-GIT_CLONE: <br>
 110 #makesrpm-GIT_CHECKOUT: HEAD </p>
 111
 112 <p>to set environment variables named without the lower case prefix. The
 113 meaning of these is explained below:<br>
 114 <br>
 115 <strong>SOURCE_PATHS</strong> - this is a space-separated list of directories
 116 relative to the top level git folder, and specifies the folders to be exported.
 117 Some git trees contain source for more than one project and so it can be
 118 convenient to reduce the size of the source tar.gz by putting a line like this
 119 in the sub-project spec file:<br>
 120 </p>
 121
 122 <blockquote>
 123   <tt>#make-srpm-SOURCE_PATHS: sub_project_dir includes</tt><br>
 124 </blockquote>
 125 <strong>ORIGIN</strong> - this is a git reference to the commit that represents
 126 the <em>pristine source</em> and should probably be the most recent tag before
 127 the git rebase point. This can be a tag or a commit hash.<br>
 128 <br>
 129 <strong>ORIGIN_PATTERN</strong> - more useful than origin, can be a git tag
 130 glob so that make-srpm can select the current ORIGIN automatically. It can be
 131 convenient to have a line in a spec file like:<br>
 132
 133
 134 <blockquote>
 135   <tt>#make-srpm-ORIGIN_PATTERN=*release*</tt><br>
 136 </blockquote>
 137 <strong>RELEASE</strong> - is a git reference to the release that you want to
 138 build; thus patches will be emitted from ORIGIN to RELEASE. This can be a tag
 139 or a commit hash, or the value HEAD (meaning whatever is currently checked
 140 out), or the special value LOCAL which means that uncommitted changes are also
 141 included.<br>
 142 <br>
 143 <strong>PATCH_LEVEL</strong> - indicates the value of the -p argument that will
 144 need passing to patch and depends on what level of subdirectory your source
 145 sits at from the top level git directory. As the value is not likely to change
 146 for a project, it can be convenient to add a line like this to a spec file:<br>
 147
 148
 149 <blockquote>
 150   <tt>#make-srpm-PATCH_LEVEL=2</tt><br>
 151 </blockquote>
 152 The new spec file will also contain some convenient macro definitions at the
 153 top of the file, like:<br>
 154
 155
 156 <blockquote>
 157   <tt>%define makesrpm_tarname samba-release-4-0-0alpha7.tar.gz<br>
 158   %define makesrpm_tarprefix samba-release-4-0-0alpha7</tt><br>
 159 </blockquote>
 160 which you can use as a basis for your own macro definitions or package
 161 fields.<br>
 162 <br>
 163 make-srpm will also allow you to pass your own spec file macro definitions.
 164 Macros may be literal macros, or interpolated macros which are be defined in
 165 terms of values calculated during execution. This is similar to defining
 166 evironment variables, except that <em>define_</em> or <em>_define_</em> is
 167 prefixed to the name.<br>
 168 <br>
 169 e.g.<br>
 170
 171
 172 <blockquote>
 173   <tt>make-srpm </tt><tt><strong><a class="moz-txt-link-abbreviated"
 174   href="/webcit/display_enter?force_room=_MAIL_&amp;recp=define_project_builder=sam@liddicott.com">define_project_builder=sam@liddicott.com</a>
 175   </strong></tt><tt>\<br>
 176   _<strong>define_project_version='$VERSION'</strong> \<strong><br>
 177   </strong> CFLAGS="-O2" \<strong><br>
 178   </strong>project.spec<br>
 179   </tt></blockquote>
 180 will replace the macro de
 181
 182 <p><br>
 183 <strong>GIT_CLONE</strong> - a git URL is cloned into a temporary folder, and
 184 then used. This allows make-srpm to run against a base spec file, and checkout
 185 the appropriate git tree. The -c flag can be used to specify a temp folder to
 186 use, which will be deleted afterwards (if empty). -C specifys a temp path to
 187 use but does not deleted it afterwards - useful to avoid repeated slow
 188 checkouts. See GIT_CHECKOUT</p>
 189
 190 <p><br>
 191 <strong>GIT_CHECKOUT</strong> - a branch or tag or hash to checkout after
 192 GIT_CLONE</p>
 193
 194 <h2>Implementation Notes</h2>
 195 <em>git rev-parse</em> is used to sanitize external git references in this
 196 manner: <br>
 197
 198
 199 <blockquote>
 200   <tt>RELEASE_COMMIT="$(git rev-parse "$RELEASE^{commit}")"</tt><br>
 201 </blockquote>
 202
 203 <h3>awk</h3>
 204 awk is used for enormous speed in some cases. <br>
 205 <br>
 206 <em>git_linearize</em> is implemented in awk and solves the problem that the
 207 output of <em>git format-patch A..B</em> will often fail when applied to A if
 208 there have been merges. git_linearize will instead take the longest path from
 209 A..B and then perform <em>git diff</em> between successive points in the path.
 210 <br>
 211 <br>
 212 <em>git_fix_empty_files</em> is implemented in awk. It processes all the
 213 outputs of <em>git diff</em> in order to cope with patches generated by <em>git
 214 diff</em> that patch cannot handle; including addition or removal of empty
 215 files and meta-data changes. Some of the metadata changes probably ought to
 216 generate shell commands to be executed once the patches have been applied.<br>
 217 <br>
 218 <em>git_check_empty_patch</em> used to be <em>grep '^'</em> which returns
 219 non-zero on empty files while passing through the entire file. Because some
 220 commits only have meta-data changes, we need to detect files without any hunks
 221 while still passing the entire output, so awk is used. <br>
 222
 223
 224 <div dir="ltr">
 225 <h3 style="text-align: center;">GNU Free Documentation License</h3>
 226
 227 <p style="text-align: center;">Version 1.3, 3 November 2008</p>
 228
 229 <p>Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
 230 &lt;<a href="http://fsf.org/">http://fsf.org/</a>&gt; </p>
 231
 232 <p>Everyone is permitted to copy and distribute verbatim copies of this license
 233 document, but changing it is not allowed.</p>
 234
 235 <h4><a name="section0"></a>0. PREAMBLE</h4>
 236
 237 <p>The purpose of this License is to make a manual, textbook, or other
 238 functional and useful document "free" in the sense of freedom: to assure
 239 everyone the effective freedom to copy and redistribute it, with or without
 240 modifying it, either commercially or noncommercially. Secondarily, this License
 241 preserves for the author and publisher a way to get credit for their work,
 242 while not being considered responsible for modifications made by others.</p>
 243
 244 <p>This License is a kind of "copyleft", which means that derivative works of
 245 the document must themselves be free in the same sense. It complements the GNU
 246 General Public License, which is a copyleft license designed for free
 247 software.</p>
 248
 249 <p>We have designed this License in order to use it for manuals for free
 250 software, because free software needs free documentation: a free program should
 251 come with manuals providing the same freedoms that the software does. But this
 252 License is not limited to software manuals; it can be used for any textual
 253 work, regardless of subject matter or whether it is published as a printed
 254 book. We recommend this License principally for works whose purpose is
 255 instruction or reference.</p>
 256
 257 <h4><a name="section1"></a>1. APPLICABILITY AND DEFINITIONS</h4>
 258
 259 <p>This License applies to any manual or other work, in any medium, that
 260 contains a notice placed by the copyright holder saying it can be distributed
 261 under the terms of this License. Such a notice grants a world-wide,
 262 royalty-free license, unlimited in duration, to use that work under the
 263 conditions stated herein. The "Document", below, refers to any such manual or
 264 work. Any member of the public is a licensee, and is addressed as "you". You
 265 accept the license if you copy, modify or distribute the work in a way
 266 requiring permission under copyright law.</p>
 267
 268 <p>A "Modified Version" of the Document means any work containing the Document
 269 or a portion of it, either copied verbatim, or with modifications and/or
 270 translated into another language.</p>
 271
 272 <p>A "Secondary Section" is a named appendix or a front-matter section of the
 273 Document that deals exclusively with the relationship of the publishers or
 274 authors of the Document to the Document's overall subject (or to related
 275 matters) and contains nothing that could fall directly within that overall
 276 subject. (Thus, if the Document is in part a textbook of mathematics, a
 277 Secondary Section may not explain any mathematics.) The relationship could be a
 278 matter of historical connection with the subject or with related matters, or of
 279 legal, commercial, philosophical, ethical or political position regarding
 280 them.</p>
 281
 282 <p>The "Invariant Sections" are certain Secondary Sections whose titles are
 283 designated, as being those of Invariant Sections, in the notice that says that
 284 the Document is released under this License. If a section does not fit the
 285 above definition of Secondary then it is not allowed to be designated as
 286 Invariant. The Document may contain zero Invariant Sections. If the Document
 287 does not identify any Invariant Sections then there are none.</p>
 288
 289 <p>The "Cover Texts" are certain short passages of text that are listed, as
 290 Front-Cover Texts or Back-Cover Texts, in the notice that says that the
 291 Document is released under this License. A Front-Cover Text may be at most 5
 292 words, and a Back-Cover Text may be at most 25 words.</p>
 293
 294 <p>A "Transparent" copy of the Document means a machine-readable copy,
 295 represented in a format whose specification is available to the general public,
 296 that is suitable for revising the document straightforwardly with generic text
 297 editors or (for images composed of pixels) generic paint programs or (for
 298 drawings) some widely available drawing editor, and that is suitable for input
 299 to text formatters or for automatic translation to a variety of formats
 300 suitable for input to text formatters. A copy made in an otherwise Transparent
 301 file format whose markup, or absence of markup, has been arranged to thwart or
 302 discourage subsequent modification by readers is not Transparent. An image
 303 format is not Transparent if used for any substantial amount of text. A copy
 304 that is not "Transparent" is called "Opaque".</p>
 305
 306 <p>Examples of suitable formats for Transparent copies include plain ASCII
 307 without markup, Texinfo input format, LaTeX input format, SGML or XML using a
 308 publicly available DTD, and standard-conforming simple HTML, PostScript or PDF
 309 designed for human modification. Examples of transparent image formats include
 310 PNG, XCF and JPG. Opaque formats include proprietary formats that can be read
 311 and edited only by proprietary word processors, SGML or XML for which the DTD
 312 and/or processing tools are not generally available, and the machine-generated
 313 HTML, PostScript or PDF produced by some word processors for output purposes
 314 only.</p>
 315
 316 <p>The "Title Page" means, for a printed book, the title page itself, plus such
 317 following pages as are needed to hold, legibly, the material this License
 318 requires to appear in the title page. For works in formats which do not have
 319 any title page as such, "Title Page" means the text near the most prominent
 320 appearance of the work's title, preceding the beginning of the body of the
 321 text.</p>
 322
 323 <p>The "publisher" means any person or entity that distributes copies of the
 324 Document to the public.</p>
 325
 326 <p>A section "Entitled XYZ" means a named subunit of the Document whose title
 327 either is precisely XYZ or contains XYZ in parentheses following text that
 328 translates XYZ in another language. (Here XYZ stands for a specific section
 329 name mentioned below, such as "Acknowledgements", "Dedications",
 330 "Endorsements", or "History".) To "Preserve the Title" of such a section when
 331 you modify the Document means that it remains a section "Entitled XYZ"
 332 according to this definition.</p>
 333
 334 <p>The Document may include Warranty Disclaimers next to the notice which
 335 states that this License applies to the Document. These Warranty Disclaimers
 336 are considered to be included by reference in this License, but only as regards
 337 disclaiming warranties: any other implication that these Warranty Disclaimers
 338 may have is void and has no effect on the meaning of this License.</p>
 339
 340 <h4><a name="section2"></a>2. VERBATIM COPYING</h4>
 341
 342 <p>You may copy and distribute the Document in any medium, either commercially
 343 or noncommercially, provided that this License, the copyright notices, and the
 344 license notice saying this License applies to the Document are reproduced in
 345 all copies, and that you add no other conditions whatsoever to those of this
 346 License. You may not use technical measures to obstruct or control the reading
 347 or further copying of the copies you make or distribute. However, you may
 348 accept compensation in exchange for copies. If you distribute a large enough
 349 number of copies you must also follow the conditions in section 3.</p>
 350
 351 <p>You may also lend copies, under the same conditions stated above, and you
 352 may publicly display copies.</p>
 353
 354 <h4><a name="section3"></a>3. COPYING IN QUANTITY</h4>
 355
 356 <p>If you publish printed copies (or copies in media that commonly have printed
 357 covers) of the Document, numbering more than 100, and the Document's license
 358 notice requires Cover Texts, you must enclose the copies in covers that carry,
 359 clearly and legibly, all these Cover Texts: Front-Cover Texts on the front
 360 cover, and Back-Cover Texts on the back cover. Both covers must also clearly
 361 and legibly identify you as the publisher of these copies. The front cover must
 362 present the full title with all words of the title equally prominent and
 363 visible. You may add other material on the covers in addition. Copying with
 364 changes limited to the covers, as long as they preserve the title of the
 365 Document and satisfy these conditions, can be treated as verbatim copying in
 366 other respects.</p>
 367
 368 <p>If the required texts for either cover are too voluminous to fit legibly,
 369 you should put the first ones listed (as many as fit reasonably) on the actual
 370 cover, and continue the rest onto adjacent pages.</p>
 371
 372 <p>If you publish or distribute Opaque copies of the Document numbering more
 373 than 100, you must either include a machine-readable Transparent copy along
 374 with each Opaque copy, or state in or with each Opaque copy a computer-network
 375 location from which the general network-using public has access to download
 376 using public-standard network protocols a complete Transparent copy of the
 377 Document, free of added material. If you use the latter option, you must take
 378 reasonably prudent steps, when you begin distribution of Opaque copies in
 379 quantity, to ensure that this Transparent copy will remain thus accessible at
 380 the stated location until at least one year after the last time you distribute
 381 an Opaque copy (directly or through your agents or retailers) of that edition
 382 to the public.</p>
 383
 384 <p>It is requested, but not required, that you contact the authors of the
 385 Document well before redistributing any large number of copies, to give them a
 386 chance to provide you with an updated version of the Document.</p>
 387
 388 <h4><a name="section4"></a>4. MODIFICATIONS</h4>
 389
 390 <p>You may copy and distribute a Modified Version of the Document under the
 391 conditions of sections 2 and 3 above, provided that you release the Modified
 392 Version under precisely this License, with the Modified Version filling the
 393 role of the Document, thus licensing distribution and modification of the
 394 Modified Version to whoever possesses a copy of it. In addition, you must do
 395 these things in the Modified Version:</p>
 396 <ul>
 397   <li>A. Use in the Title Page (and on the covers, if any) a title distinct
 398     from that of the Document, and from those of previous versions (which
 399     should, if there were any, be listed in the History section of the
 400     Document). You may use the same title as a previous version if the original
 401     publisher of that version gives permission. </li>
 402   <li>B. List on the Title Page, as authors, one or more persons or entities
 403     responsible for authorship of the modifications in the Modified Version,
 404     together with at least five of the principal authors of the Document (all
 405     of its principal authors, if it has fewer than five), unless they release
 406     you from this requirement. </li>
 407   <li>C. State on the Title page the name of the publisher of the Modified
 408     Version, as the publisher. </li>
 409   <li>D. Preserve all the copyright notices of the Document. </li>
 410   <li>E. Add an appropriate copyright notice for your modifications adjacent to
 411     the other copyright notices. </li>
 412   <li>F. Include, immediately after the copyright notices, a license notice
 413     giving the public permission to use the Modified Version under the terms of
 414     this License, in the form shown in the Addendum below. </li>
 415   <li>G. Preserve in that license notice the full lists of Invariant Sections
 416     and required Cover Texts given in the Document's license notice. </li>
 417   <li>H. Include an unaltered copy of this License. </li>
 418   <li>I. Preserve the section Entitled "History", Preserve its Title, and add
 419     to it an item stating at least the title, year, new authors, and publisher
 420     of the Modified Version as given on the Title Page. If there is no section
 421     Entitled "History" in the Document, create one stating the title, year,
 422     authors, and publisher of the Document as given on its Title Page, then add
 423     an item describing the Modified Version as stated in the previous sentence.
 424   </li>
 425   <li>J. Preserve the network location, if any, given in the Document for
 426     public access to a Transparent copy of the Document, and likewise the
 427     network locations given in the Document for previous versions it was based
 428     on. These may be placed in the "History" section. You may omit a network
 429     location for a work that was published at least four years before the
 430     Document itself, or if the original publisher of the version it refers to
 431     gives permission. </li>
 432   <li>K. For any section Entitled "Acknowledgements" or "Dedications", Preserve
 433     the Title of the section, and preserve in the section all the substance and
 434     tone of each of the contributor acknowledgements and/or dedications given
 435     therein. </li>
 436   <li>L. Preserve all the Invariant Sections of the Document, unaltered in
 437     their text and in their titles. Section numbers or the equivalent are not
 438     considered part of the section titles. </li>
 439   <li>M. Delete any section Entitled "Endorsements". Such a section may not be
 440     included in the Modified Version. </li>
 441   <li>N. Do not retitle any existing section to be Entitled "Endorsements" or
 442     to conflict in title with any Invariant Section. </li>
 443   <li>O. Preserve any Warranty Disclaimers.</li>
 444 </ul>
 445
 446 <p>If the Modified Version includes new front-matter sections or appendices
 447 that qualify as Secondary Sections and contain no material copied from the
 448 Document, you may at your option designate some or all of these sections as
 449 invariant. To do this, add their titles to the list of Invariant Sections in
 450 the Modified Version's license notice. These titles must be distinct from any
 451 other section titles.</p>
 452
 453 <p>You may add a section Entitled "Endorsements", provided it contains nothing
 454 but endorsements of your Modified Version by various parties&#x2014;for
 455 example, statements of peer review or that the text has been approved by an
 456 organization as the authoritative definition of a standard.</p>
 457
 458 <p>You may add a passage of up to five words as a Front-Cover Text, and a
 459 passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover
 460 Texts in the Modified Version. Only one passage of Front-Cover Text and one of
 461 Back-Cover Text may be added by (or through arrangements made by) any one
 462 entity. If the Document already includes a cover text for the same cover,
 463 previously added by you or by arrangement made by the same entity you are
 464 acting on behalf of, you may not add another; but you may replace the old one,
 465 on explicit permission from the previous publisher that added the old one.</p>
 466
 467 <p>The author(s) and publisher(s) of the Document do not by this License give
 468 permission to use their names for publicity for or to assert or imply
 469 endorsement of any Modified Version.</p>
 470
 471 <h4><a name="section5"></a>5. COMBINING DOCUMENTS</h4>
 472
 473 <p>You may combine the Document with other documents released under this
 474 License, under the terms defined in section 4 above for modified versions,
 475 provided that you include in the combination all of the Invariant Sections of
 476 all of the original documents, unmodified, and list them all as Invariant
 477 Sections of your combined work in its license notice, and that you preserve all
 478 their Warranty Disclaimers.</p>
 479
 480 <p>The combined work need only contain one copy of this License, and multiple
 481 identical Invariant Sections may be replaced with a single copy. If there are
 482 multiple Invariant Sections with the same name but different contents, make the
 483 title of each such section unique by adding at the end of it, in parentheses,
 484 the name of the original author or publisher of that section if known, or else
 485 a unique number. Make the same adjustment to the section titles in the list of
 486 Invariant Sections in the license notice of the combined work.</p>
 487
 488 <p>In the combination, you must combine any sections Entitled "History" in the
 489 various original documents, forming one section Entitled "History"; likewise
 490 combine any sections Entitled "Acknowledgements", and any sections Entitled
 491 "Dedications". You must delete all sections Entitled "Endorsements".</p>
 492
 493 <h4><a name="section6"></a>6. COLLECTIONS OF DOCUMENTS</h4>
 494
 495 <p>You may make a collection consisting of the Document and other documents
 496 released under this License, and replace the individual copies of this License
 497 in the various documents with a single copy that is included in the collection,
 498 provided that you follow the rules of this License for verbatim copying of each
 499 of the documents in all other respects.</p>
 500
 501 <p>You may extract a single document from such a collection, and distribute it
 502 individually under this License, provided you insert a copy of this License
 503 into the extracted document, and follow this License in all other respects
 504 regarding verbatim copying of that document.</p>
 505
 506 <h4><a name="section7"></a>7. AGGREGATION WITH INDEPENDENT WORKS</h4>
 507
 508 <p>A compilation of the Document or its derivatives with other separate and
 509 independent documents or works, in or on a volume of a storage or distribution
 510 medium, is called an "aggregate" if the copyright resulting from the
 511 compilation is not used to limit the legal rights of the compilation's users
 512 beyond what the individual works permit. When the Document is included in an
 513 aggregate, this License does not apply to the other works in the aggregate
 514 which are not themselves derivative works of the Document.</p>
 515
 516 <p>If the Cover Text requirement of section 3 is applicable to these copies of
 517 the Document, then if the Document is less than one half of the entire
 518 aggregate, the Document's Cover Texts may be placed on covers that bracket the
 519 Document within the aggregate, or the electronic equivalent of covers if the
 520 Document is in electronic form. Otherwise they must appear on printed covers
 521 that bracket the whole aggregate.</p>
 522
 523 <h4><a name="section8"></a>8. TRANSLATION</h4>
 524
 525 <p>Translation is considered a kind of modification, so you may distribute
 526 translations of the Document under the terms of section 4. Replacing Invariant
 527 Sections with translations requires special permission from their copyright
 528 holders, but you may include translations of some or all Invariant Sections in
 529 addition to the original versions of these Invariant Sections. You may include
 530 a translation of this License, and all the license notices in the Document, and
 531 any Warranty Disclaimers, provided that you also include the original English
 532 version of this License and the original versions of those notices and
 533 disclaimers. In case of a disagreement between the translation and the original
 534 version of this License or a notice or disclaimer, the original version will
 535 prevail.</p>
 536
 537 <p>If a section in the Document is Entitled "Acknowledgements", "Dedications",
 538 or "History", the requirement (section 4) to Preserve its Title (section 1)
 539 will typically require changing the actual title.</p>
 540
 541 <h4><a name="section9"></a>9. TERMINATION</h4>
 542
 543 <p>You may not copy, modify, sublicense, or distribute the Document except as
 544 expressly provided under this License. Any attempt otherwise to copy, modify,
 545 sublicense, or distribute it is void, and will automatically terminate your
 546 rights under this License.</p>
 547
 548 <p>However, if you cease all violation of this License, then your license from
 549 a particular copyright holder is reinstated (a) provisionally, unless and until
 550 the copyright holder explicitly and finally terminates your license, and (b)
 551 permanently, if the copyright holder fails to notify you of the violation by
 552 some reasonable means prior to 60 days after the cessation.</p>
 553
 554 <p>Moreover, your license from a particular copyright holder is reinstated
 555 permanently if the copyright holder notifies you of the violation by some
 556 reasonable means, this is the first time you have received notice of violation
 557 of this License (for any work) from that copyright holder, and you cure the
 558 violation prior to 30 days after your receipt of the notice.</p>
 559
 560 <p>Termination of your rights under this section does not terminate the
 561 licenses of parties who have received copies or rights from you under this
 562 License. If your rights have been terminated and not permanently reinstated,
 563 receipt of a copy of some or all of the same material does not give you any
 564 rights to use it.</p>
 565
 566 <h4><a name="section10"></a>10. FUTURE REVISIONS OF THIS LICENSE</h4>
 567
 568 <p>The Free Software Foundation may publish new, revised versions of the GNU
 569 Free Documentation License from time to time. Such new versions will be similar
 570 in spirit to the present version, but may differ in detail to address new
 571 problems or concerns. See <a
 572 href="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</a>.</p>
 573
 574 <p>Each version of the License is given a distinguishing version number. If the
 575 Document specifies that a particular numbered version of this License "or any
 576 later version" applies to it, you have the option of following the terms and
 577 conditions either of that specified version or of any later version that has
 578 been published (not as a draft) by the Free Software Foundation. If the
 579 Document does not specify a version number of this License, you may choose any
 580 version ever published (not as a draft) by the Free Software Foundation. If the
 581 Document specifies that a proxy can decide which future versions of this
 582 License can be used, that proxy's public statement of acceptance of a version
 583 permanently authorizes you to choose that version for the Document.</p>
 584
 585 <h4><a name="section11"></a>11. RELICENSING</h4>
 586
 587 <p>"Massive Multiauthor Collaboration Site" (or "MMC Site") means any World
 588 Wide Web server that publishes copyrightable works and also provides prominent
 589 facilities for anybody to edit those works. A public wiki that anybody can edit
 590 is an example of such a server. A "Massive Multiauthor Collaboration" (or
 591 "MMC") contained in the site means any set of copyrightable works thus
 592 published on the MMC site.</p>
 593
 594 <p>"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 license
 595 published by Creative Commons Corporation, a not-for-profit corporation with a
 596 principal place of business in San Francisco, California, as well as future
 597 copyleft versions of that license published by that same organization.</p>
 598
 599 <p>"Incorporate" means to publish or republish a Document, in whole or in part,
 600 as part of another Document.</p>
 601
 602 <p>An MMC is "eligible for relicensing" if it is licensed under this License,
 603 and if all works that were first published under this License somewhere other
 604 than this MMC, and subsequently incorporated in whole or in part into the MMC,
 605 (1) had no cover texts or invariant sections, and (2) were thus incorporated
 606 prior to November 1, 2008.</p>
 607
 608 <p>The operator of an MMC Site may republish an MMC contained in the site under
 609 CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC
 610 is eligible for relicensing.</p>
 611 </div>
 612 </div>
 613 </body>
 614 </html>