[Demudi-commits] r796 - in rosegarden: branches/upstream/1.2.3
trunk trunk/debian trunk/debian/patches
Free Ekanayaka
free-guest at costa.debian.org
Wed Jun 7 10:25:15 UTC 2006
Author: free-guest
Date: 2006-06-07 10:25:09 +0000 (Wed, 07 Jun 2006)
New Revision: 796
Added:
rosegarden/trunk/debian/patches/
rosegarden/trunk/debian/patches/00list
rosegarden/trunk/debian/patches/10_install-list.dpatch
rosegarden/trunk/debian/patches/20_env.dpatch
Removed:
rosegarden/branches/upstream/1.2.3/AUTHORS
rosegarden/branches/upstream/1.2.3/COPYING
rosegarden/branches/upstream/1.2.3/Doxyfile
rosegarden/branches/upstream/1.2.3/README
rosegarden/branches/upstream/1.2.3/SConstruct
rosegarden/branches/upstream/1.2.3/TRANSLATORS
rosegarden/branches/upstream/1.2.3/base/
rosegarden/branches/upstream/1.2.3/docs/
rosegarden/branches/upstream/1.2.3/gui/
rosegarden/branches/upstream/1.2.3/po/
rosegarden/branches/upstream/1.2.3/rosegarden.lsm
rosegarden/branches/upstream/1.2.3/scons_admin/
rosegarden/branches/upstream/1.2.3/scripts/
rosegarden/branches/upstream/1.2.3/sequencer/
rosegarden/branches/upstream/1.2.3/sound/
rosegarden/trunk/AUTHORS
rosegarden/trunk/COPYING
rosegarden/trunk/Doxyfile
rosegarden/trunk/README
rosegarden/trunk/SConstruct
rosegarden/trunk/TRANSLATORS
rosegarden/trunk/base/
rosegarden/trunk/docs/
rosegarden/trunk/gui/
rosegarden/trunk/po/
rosegarden/trunk/rosegarden.lsm
rosegarden/trunk/scons_admin/
rosegarden/trunk/scripts/
rosegarden/trunk/sequencer/
rosegarden/trunk/sound/
rosegarden/trunk/version.txt
Modified:
rosegarden/trunk/debian/
rosegarden/trunk/debian/changelog
rosegarden/trunk/debian/control
rosegarden/trunk/debian/rules
Log:
Remove upstream sources from the repository
Deleted: rosegarden/branches/upstream/1.2.3/AUTHORS
===================================================================
--- rosegarden/branches/upstream/1.2.3/AUTHORS 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/branches/upstream/1.2.3/AUTHORS 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,112 +0,0 @@
-Lead developers:
-
-Chris Cannam <cannam at all-day-breakfast.com>
-Richard Bown <bownie at bownie.com>
-Guillaume Laurent <glaurent at telegraph-road.org>
-
-Adjunct developers:
-
-D. Michael McIntyre <dmmcintyr at users.sourceforge.net>
-
-
-Contributors:
-
-Ron Kuris <rk at prefer.net>
- * cleanups
-
-Randall Farmer <rfarme at simons-rock.edu>
- * chord labelling code
-
-Hans Kieserman <hkieserman at mail.com>
- * Lilypond output
- * assorted other patches
- * i18n-ization
-
-Levi Burton <donburton at sbcglobal.net>
- * UI improvements
- * other bug fixes
-
-Mark Hymers <markh at linuxfromscratch.org>
- * Segment colours
- * Other UI and bug fixes
-
-Alexandre Prokoudine <alexandre.prokoudine at gmail.com>
- * Russian translation
- * i18n-ization
-
-Pedro Lopez-Cabanillas <plcl at users.sourceforge.net>
- * Spanish translation
- * ALSA hacking and bug fixes
- * multi-input MIDI recording
-
-Jörg Schumann <jrschumann at gmx.de>
-Eckhard Jokisch <e.jokisch at u-code.de>
- * German translation
-
-Kevin Donnelly
- * Welsh translation
-
-Didier Burli
- * French translation
-
-Daniele Medri
-Alessandro Musesti
- * Italian translation
-
-Stefan Asserh�l
-Erik Magnus Johansson
- * Swedish translation
-
-Hasso Tepper
- * Estonian translation
-
-Jelmer Vernooij
- * Dutch translation
-
-Oota Toshiya
- * Japanese translation
-
-Kevin Liang
- * HSpinBox class
-
-Thorsten Wilms
- * Original designs on which the Rosegarden rotary controllers are based
-
-William <rosegarden4c AT orthoset.com>
- * auto-scroll deceleration
- * glyphs for rests outside staves and other bug fixes
-
-Liu Songhe <jackliu9999 AT msn.com>
- * Simplified Chinese translation
-
-Thomas Nagy <tnagy256 at yahoo.fr>
- * SCons/bksys building system
-
-Vince Negri <vince-rg at bulbous.freeserve.co.uk>
- * Initial MTC slave implementation (the bits without the bugs)
-
-Toni Arnold <toni__arnold at bluewin.ch>
- * LIRC infrared remote-controller support
-
-Jan B�a <jbina at sky.cz>
- * Czech translation
-
-Vladimir Savic <vladimir at vladimirsavic.net>
- * icons, icons, icons
-
-Lisandro Damián Nicanor Pérez Meyer <perezmeyer at infovia.com.ar>
-Javier Castrillo <riverplatense at gmail.com>
-Lucas Godoy <godoy.lucas at gmail.com>
-Marcos Guglielmetti <marcospcmusica at yahoo.com.ar>
- * Spanish translation
-
-Feliu Ferrer <mverge2 at pie.xtec.es>
-Quim Perez i Noguer <noguer at osona.com>
- * Catalan translation
-
-Carolyn McIntyre <catma at adelphia.net>
- * new splash screen photo (of Michael McIntyre's rose garden)
-
-##
-## Names in here should also be credited in gui/main.cpp, with aboutData.addCredit()
-##
Deleted: rosegarden/branches/upstream/1.2.3/COPYING
===================================================================
--- rosegarden/branches/upstream/1.2.3/COPYING 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/branches/upstream/1.2.3/COPYING 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,280 +0,0 @@
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 675 Mass Ave, Cambridge, MA 02139, USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
Deleted: rosegarden/branches/upstream/1.2.3/Doxyfile
===================================================================
--- rosegarden/branches/upstream/1.2.3/Doxyfile 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/branches/upstream/1.2.3/Doxyfile 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,753 +0,0 @@
-# Doxyfile 1.2.5
-
-# This file describes the settings to be used by doxygen for a project
-#
-# All text after a hash (#) is considered a comment and will be ignored
-# The format is:
-# TAG = value [value, ...]
-# For lists items can also be appended using:
-# TAG += value [value, ...]
-# Values that contain spaces should be placed between quotes (" ")
-
-#---------------------------------------------------------------------------
-# General configuration options
-#---------------------------------------------------------------------------
-
-# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
-# by quotes) that should identify the project.
-
-PROJECT_NAME = Rosegarden
-
-# The PROJECT_NUMBER tag can be used to enter a project or revision number.
-# This could be handy for archiving the generated documentation or
-# if some version control system is used.
-
-PROJECT_NUMBER = 0.1
-
-# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
-# base path where the generated documentation will be put.
-# If a relative path is entered, it will be relative to the location
-# where doxygen was started. If left blank the current directory will be used.
-
-OUTPUT_DIRECTORY = docs/doxygen
-
-# The OUTPUT_LANGUAGE tag is used to specify the language in which all
-# documentation generated by doxygen is written. Doxygen will use this
-# information to generate all constant output in the proper language.
-# The default language is English, other supported languages are:
-# Dutch, French, Italian, Czech, Swedish, German, Finnish, Japanese,
-# Korean, Hungarian, Norwegian, Spanish, Romanian, Russian, Croatian,
-# Polish, Portuguese and Slovene.
-
-OUTPUT_LANGUAGE = English
-
-# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
-# documentation are documented, even if no documentation was available.
-# Private class members and static file members will be hidden unless
-# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
-
-EXTRACT_ALL = YES
-
-# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
-# will be included in the documentation.
-
-EXTRACT_PRIVATE = NO
-
-# If the EXTRACT_STATIC tag is set to YES all static members of a file
-# will be included in the documentation.
-
-EXTRACT_STATIC = NO
-
-# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
-# undocumented members of documented classes, files or namespaces.
-# If set to NO (the default) these members will be included in the
-# various overviews, but no documentation section is generated.
-# This option has no effect if EXTRACT_ALL is enabled.
-
-HIDE_UNDOC_MEMBERS = NO
-
-# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
-# undocumented classes that are normally visible in the class hierarchy.
-# If set to NO (the default) these class will be included in the various
-# overviews. This option has no effect if EXTRACT_ALL is enabled.
-
-HIDE_UNDOC_CLASSES = NO
-
-# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
-# include brief member descriptions after the members that are listed in
-# the file and class documentation (similar to JavaDoc).
-# Set to NO to disable this.
-
-BRIEF_MEMBER_DESC = YES
-
-# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
-# the brief description of a member or function before the detailed description.
-# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
-# brief descriptions will be completely suppressed.
-
-REPEAT_BRIEF = YES
-
-# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
-# Doxygen will generate a detailed section even if there is only a brief
-# description.
-
-ALWAYS_DETAILED_SEC = NO
-
-# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
-# path before files name in the file list and in the header files. If set
-# to NO the shortest path that makes the file name unique will be used.
-
-FULL_PATH_NAMES = NO
-
-# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
-# can be used to strip a user defined part of the path. Stripping is
-# only done if one of the specified strings matches the left-hand part of
-# the path. It is allowed to use relative paths in the argument list.
-
-STRIP_FROM_PATH =
-
-# The INTERNAL_DOCS tag determines if documentation
-# that is typed after a \internal command is included. If the tag is set
-# to NO (the default) then the documentation will be excluded.
-# Set it to YES to include the internal documentation.
-
-INTERNAL_DOCS = NO
-
-# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
-# generate a class diagram (in Html and LaTeX) for classes with base or
-# super classes. Setting the tag to NO turns the diagrams off.
-
-CLASS_DIAGRAMS = YES
-
-# If the SOURCE_BROWSER tag is set to YES then a list of source files will
-# be generated. Documented entities will be cross-referenced with these sources.
-
-SOURCE_BROWSER = NO
-
-# Setting the INLINE_SOURCES tag to YES will include the body
-# of functions and classes directly in the documentation.
-
-INLINE_SOURCES = NO
-
-# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
-# doxygen to hide any special comment blocks from generated source code
-# fragments. Normal C and C++ comments will always remain visible.
-
-STRIP_CODE_COMMENTS = YES
-
-# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
-# file names in lower case letters. If set to YES upper case letters are also
-# allowed. This is useful if you have classes or files whose names only differ
-# in case and if your file system supports case sensitive file names. Windows
-# users are adviced to set this option to NO.
-
-CASE_SENSE_NAMES = YES
-
-# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
-# will show members with their full class and namespace scopes in the
-# documentation. If set to YES the scope will be hidden.
-
-HIDE_SCOPE_NAMES = NO
-
-# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
-# will generate a verbatim copy of the header file for each class for
-# which an include is specified. Set to NO to disable this.
-
-VERBATIM_HEADERS = YES
-
-# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
-# will put list of the files that are included by a file in the documentation
-# of that file.
-
-SHOW_INCLUDE_FILES = YES
-
-# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
-# will interpret the first line (until the first dot) of a JavaDoc-style
-# comment as the brief description. If set to NO, the JavaDoc
-# comments will behave just like the Qt-style comments (thus requiring an
-# explict @brief command for a brief description.
-
-JAVADOC_AUTOBRIEF = NO
-
-# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
-# member inherits the documentation from any documented member that it
-# reimplements.
-
-INHERIT_DOCS = YES
-
-# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
-# is inserted in the documentation for inline members.
-
-INLINE_INFO = YES
-
-# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
-# will sort the (detailed) documentation of file and class members
-# alphabetically by member name. If set to NO the members will appear in
-# declaration order.
-
-SORT_MEMBER_DOCS = YES
-
-# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
-# tag is set to YES, then doxygen will reuse the documentation of the first
-# member in the group (if any) for the other members of the group. By default
-# all members of a group must be documented explicitly.
-
-DISTRIBUTE_GROUP_DOC = NO
-
-# The TAB_SIZE tag can be used to set the number of spaces in a tab.
-# Doxygen uses this value to replace tabs by spaces in code fragments.
-
-TAB_SIZE = 8
-
-# The ENABLE_SECTIONS tag can be used to enable conditional
-# documentation sections, marked by \if sectionname ... \endif.
-
-ENABLED_SECTIONS =
-
-# The GENERATE_TODOLIST tag can be used to enable (YES) or
-# disable (NO) the todo list. This list is created by putting \todo
-# commands in the documentation.
-
-GENERATE_TODOLIST = YES
-
-# The GENERATE_TESTLIST tag can be used to enable (YES) or
-# disable (NO) the test list. This list is created by putting \test
-# commands in the documentation.
-
-GENERATE_TESTLIST = YES
-
-# This tag can be used to specify a number of aliases that acts
-# as commands in the documentation. An alias has the form "name=value".
-# For example adding "sideeffect=\par Side Effects:\n" will allow you to
-# put the command \sideeffect (or @sideeffect) in the documentation, which
-# will result in a user defined paragraph with heading "Side Effects:".
-# You can put \n's in the value part of an alias to insert newlines.
-
-ALIASES =
-
-# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
-# the initial value of a variable or define consist of for it to appear in
-# the documentation. If the initializer consists of more lines than specified
-# here it will be hidden. Use a value of 0 to hide initializers completely.
-# The appearance of the initializer of individual variables and defines in the
-# documentation can be controlled using \showinitializer or \hideinitializer
-# command in the documentation regardless of this setting.
-
-MAX_INITIALIZER_LINES = 30
-
-# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
-# only. Doxygen will then generate output that is more tailored for C.
-# For instance some of the names that are used will be different. The list
-# of all members will be omitted, etc.
-
-OPTIMIZE_OUTPUT_FOR_C = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to warning and progress messages
-#---------------------------------------------------------------------------
-
-# The QUIET tag can be used to turn on/off the messages that are generated
-# by doxygen. Possible values are YES and NO. If left blank NO is used.
-
-QUIET = NO
-
-# The WARNINGS tag can be used to turn on/off the warning messages that are
-# generated by doxygen. Possible values are YES and NO. If left blank
-# NO is used.
-
-WARNINGS = YES
-
-# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
-# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
-# automatically be disabled.
-
-WARN_IF_UNDOCUMENTED = YES
-
-# The WARN_FORMAT tag determines the format of the warning messages that
-# doxygen can produce. The string should contain the $file, $line, and $text
-# tags, which will be replaced by the file and line number from which the
-# warning originated and the warning text.
-
-WARN_FORMAT = "$file:$line: $text"
-
-# The WARN_LOGFILE tag can be used to specify a file to which warning
-# and error messages should be written. If left blank the output is written
-# to stderr.
-
-WARN_LOGFILE =
-
-#---------------------------------------------------------------------------
-# configuration options related to the input files
-#---------------------------------------------------------------------------
-
-# The INPUT tag can be used to specify the files and/or directories that contain
-# documented source files. You may enter file names like "myfile.cpp" or
-# directories like "/usr/src/myproject". Separate the files or directories
-# with spaces.
-
-INPUT = base sound sequencer gui
-#INPUT = gui/main.cpp
-
-# If the value of the INPUT tag contains directories, you can use the
-# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
-# and *.h) to filter out the source-files in the directories. If left
-# blank all files are included.
-
-FILE_PATTERNS = *.h *.C *.cpp *.cc
-
-# The RECURSIVE tag can be used to turn specify whether or not subdirectories
-# should be searched for input files as well. Possible values are YES and NO.
-# If left blank NO is used.
-
-RECURSIVE = NO
-
-# The EXCLUDE tag can be used to specify files and/or directories that should
-# excluded from the INPUT source files. This way you can easily exclude a
-# subdirectory from a directory tree whose root is specified with the INPUT tag.
-
-EXCLUDE =
-
-# If the value of the INPUT tag contains directories, you can use the
-# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
-# certain files from those directories.
-
-EXCLUDE_PATTERNS = *.moc.cpp *_skel.cpp
-
-# The EXAMPLE_PATH tag can be used to specify one or more files or
-# directories that contain example code fragments that are included (see
-# the \include command).
-
-EXAMPLE_PATH =
-
-# If the value of the EXAMPLE_PATH tag contains directories, you can use the
-# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
-# and *.h) to filter out the source-files in the directories. If left
-# blank all files are included.
-
-EXAMPLE_PATTERNS =
-
-# The IMAGE_PATH tag can be used to specify one or more files or
-# directories that contain image that are included in the documentation (see
-# the \image command).
-
-IMAGE_PATH =
-
-# The INPUT_FILTER tag can be used to specify a program that doxygen should
-# invoke to filter for each input file. Doxygen will invoke the filter program
-# by executing (via popen()) the command <filter> <input-file>, where <filter>
-# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
-# input file. Doxygen will then use the output that the filter program writes
-# to standard output.
-
-INPUT_FILTER =
-
-# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
-# INPUT_FILTER) will be used to filter the input files when producing source
-# files to browse.
-
-FILTER_SOURCE_FILES = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the alphabetical class index
-#---------------------------------------------------------------------------
-
-# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
-# of all compounds will be generated. Enable this if the project
-# contains a lot of classes, structs, unions or interfaces.
-
-ALPHABETICAL_INDEX = NO
-
-# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
-# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
-# in which this list will be split (can be a number in the range [1..20])
-
-COLS_IN_ALPHA_INDEX = 5
-
-# In case all classes in a project start with a common prefix, all
-# classes will be put under the same header in the alphabetical index.
-# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
-# should be ignored while generating the index headers.
-
-IGNORE_PREFIX =
-
-#---------------------------------------------------------------------------
-# configuration options related to the HTML output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
-# generate HTML output.
-
-GENERATE_HTML = YES
-
-# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `html' will be used as the default path.
-
-HTML_OUTPUT = html
-
-# The HTML_HEADER tag can be used to specify a personal HTML header for
-# each generated HTML page. If it is left blank doxygen will generate a
-# standard header.
-
-HTML_HEADER =
-
-# The HTML_FOOTER tag can be used to specify a personal HTML footer for
-# each generated HTML page. If it is left blank doxygen will generate a
-# standard footer.
-
-HTML_FOOTER =
-
-# The HTML_STYLESHEET tag can be used to specify a user defined cascading
-# style sheet that is used by each HTML page. It can be used to
-# fine-tune the look of the HTML output. If the tag is left blank doxygen
-# will generate a default style sheet
-
-HTML_STYLESHEET =
-
-# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
-# files or namespaces will be aligned in HTML using tables. If set to
-# NO a bullet list will be used.
-
-HTML_ALIGN_MEMBERS = YES
-
-# If the GENERATE_HTMLHELP tag is set to YES, additional index files
-# will be generated that can be used as input for tools like the
-# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
-# of the generated HTML documentation.
-
-GENERATE_HTMLHELP = NO
-
-# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
-# top of each HTML page. The value NO (the default) enables the index and
-# the value YES disables it.
-
-DISABLE_INDEX = NO
-
-# This tag can be used to set the number of enum values (range [1..20])
-# that doxygen will group on one line in the generated HTML documentation.
-
-ENUM_VALUES_PER_LINE = 4
-
-# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
-# generated containing a tree-like index structure (just like the one that
-# is generated for HTML Help). For this to work a browser that supports
-# JavaScript and frames is required (for instance Netscape 4.0+
-# or Internet explorer 4.0+).
-
-GENERATE_TREEVIEW = NO
-
-# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
-# used to set the initial width (in pixels) of the frame in which the tree
-# is shown.
-
-TREEVIEW_WIDTH = 250
-
-#---------------------------------------------------------------------------
-# configuration options related to the LaTeX output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
-# generate Latex output.
-
-GENERATE_LATEX = NO
-
-# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `latex' will be used as the default path.
-
-LATEX_OUTPUT = latex
-
-# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
-# LaTeX documents. This may be useful for small projects and may help to
-# save some trees in general.
-
-COMPACT_LATEX = NO
-
-# The PAPER_TYPE tag can be used to set the paper type that is used
-# by the printer. Possible values are: a4, a4wide, letter, legal and
-# executive. If left blank a4wide will be used.
-
-PAPER_TYPE = a4wide
-
-# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
-# packages that should be included in the LaTeX output.
-
-EXTRA_PACKAGES =
-
-# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
-# the generated latex document. The header should contain everything until
-# the first chapter. If it is left blank doxygen will generate a
-# standard header. Notice: only use this tag if you know what you are doing!
-
-LATEX_HEADER =
-
-# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
-# is prepared for conversion to pdf (using ps2pdf). The pdf file will
-# contain links (just like the HTML output) instead of page references
-# This makes the output suitable for online browsing using a pdf viewer.
-
-PDF_HYPERLINKS = NO
-
-# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
-# plain latex in the generated Makefile. Set this option to YES to get a
-# higher quality PDF documentation.
-
-USE_PDFLATEX = NO
-
-# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
-# command to the generated LaTeX files. This will instruct LaTeX to keep
-# running if errors occur, instead of asking the user for help.
-# This option is also used when generating formulas in HTML.
-
-LATEX_BATCHMODE = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the RTF output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
-# The RTF output is optimised for Word 97 and may not look very pretty with
-# other RTF readers or editors.
-
-GENERATE_RTF = NO
-
-# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `rtf' will be used as the default path.
-
-RTF_OUTPUT = rtf
-
-# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
-# RTF documents. This may be useful for small projects and may help to
-# save some trees in general.
-
-COMPACT_RTF = NO
-
-# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
-# will contain hyperlink fields. The RTF file will
-# contain links (just like the HTML output) instead of page references.
-# This makes the output suitable for online browsing using a WORD or other.
-# programs which support those fields.
-# Note: wordpad (write) and others do not support links.
-
-RTF_HYPERLINKS = NO
-
-# Load stylesheet definitions from file. Syntax is similar to doxygen's
-# config file, i.e. a series of assigments. You only have to provide
-# replacements, missing definitions are set to their default value.
-
-RTF_STYLESHEET_FILE =
-
-#---------------------------------------------------------------------------
-# configuration options related to the man page output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
-# generate man pages
-
-GENERATE_MAN = NO
-
-# The MAN_OUTPUT tag is used to specify where the man pages will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `man' will be used as the default path.
-
-MAN_OUTPUT = man
-
-# The MAN_EXTENSION tag determines the extension that is added to
-# the generated man pages (default is the subroutine's section .3)
-
-MAN_EXTENSION = .3
-
-#---------------------------------------------------------------------------
-# Configuration options related to the preprocessor
-#---------------------------------------------------------------------------
-
-# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
-# evaluate all C-preprocessor directives found in the sources and include
-# files.
-
-ENABLE_PREPROCESSING = YES
-
-# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
-# names in the source code. If set to NO (the default) only conditional
-# compilation will be performed. Macro expansion can be done in a controlled
-# way by setting EXPAND_ONLY_PREDEF to YES.
-
-MACRO_EXPANSION = NO
-
-# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
-# then the macro expansion is limited to the macros specified with the
-# PREDEFINED and EXPAND_AS_PREDEFINED tags.
-
-EXPAND_ONLY_PREDEF = NO
-
-# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
-# in the INCLUDE_PATH (see below) will be search if a #include is found.
-
-SEARCH_INCLUDES = YES
-
-# The INCLUDE_PATH tag can be used to specify one or more directories that
-# contain include files that are not input files but should be processed by
-# the preprocessor.
-
-INCLUDE_PATH =
-
-# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
-# patterns (like *.h and *.hpp) to filter out the header-files in the
-# directories. If left blank, the patterns specified with FILE_PATTERNS will
-# be used.
-
-INCLUDE_FILE_PATTERNS =
-
-# The PREDEFINED tag can be used to specify one or more macro names that
-# are defined before the preprocessor is started (similar to the -D option of
-# gcc). The argument of the tag is a list of macros of the form: name
-# or name=definition (no spaces). If the definition and the = are
-# omitted =1 is assumed.
-
-PREDEFINED =
-
-# If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
-# this tag can be used to specify a list of macro names that should be expanded.
-# The macro definition that is found in the sources will be used.
-# Use the PREDEFINED tag if you want to use a different macro definition.
-
-EXPAND_AS_DEFINED =
-
-#---------------------------------------------------------------------------
-# Configuration::addtions related to external references
-#---------------------------------------------------------------------------
-
-# The TAGFILES tag can be used to specify one or more tagfiles.
-
-TAGFILES =
-
-# When a file name is specified after GENERATE_TAGFILE, doxygen will create
-# a tag file that is based on the input files it reads.
-
-GENERATE_TAGFILE =
-
-# If the ALLEXTERNALS tag is set to YES all external classes will be listed
-# in the class index. If set to NO only the inherited external classes
-# will be listed.
-
-ALLEXTERNALS = NO
-
-# The PERL_PATH should be the absolute path and name of the perl script
-# interpreter (i.e. the result of `which perl').
-
-PERL_PATH = /usr/bin/perl
-
-#---------------------------------------------------------------------------
-# Configuration options related to the dot tool
-#---------------------------------------------------------------------------
-
-# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
-# available from the path. This tool is part of Graphviz, a graph visualization
-# toolkit from AT&T and Lucent Bell Labs. The other options in this section
-# have no effect if this option is set to NO (the default)
-
-HAVE_DOT = NO
-
-# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
-# will generate a graph for each documented class showing the direct and
-# indirect inheritance relations. Setting this tag to YES will force the
-# the CLASS_DIAGRAMS tag to NO.
-
-CLASS_GRAPH = YES
-
-# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
-# will generate a graph for each documented class showing the direct and
-# indirect implementation dependencies (inheritance, containment, and
-# class references variables) of the class with other documented classes.
-
-COLLABORATION_GRAPH = YES
-
-# If the ENABLE_PREPROCESSING, INCLUDE_GRAPH, and HAVE_DOT tags are set to
-# YES then doxygen will generate a graph for each documented file showing
-# the direct and indirect include dependencies of the file with other
-# documented files.
-
-INCLUDE_GRAPH = YES
-
-# If the ENABLE_PREPROCESSING, INCLUDED_BY_GRAPH, and HAVE_DOT tags are set to
-# YES then doxygen will generate a graph for each documented header file showing
-# the documented files that directly or indirectly include this file
-
-INCLUDED_BY_GRAPH = YES
-
-# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
-# will graphical hierarchy of all classes instead of a textual one.
-
-GRAPHICAL_HIERARCHY = YES
-
-# The tag DOT_PATH can be used to specify the path where the dot tool can be
-# found. If left blank, it is assumed the dot tool can be found on the path.
-
-DOT_PATH =
-
-# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
-# (in pixels) of the graphs generated by dot. If a graph becomes larger than
-# this value, doxygen will try to truncate the graph, so that it fits within
-# the specified constraint. Beware that most browsers cannot cope with very
-# large images.
-
-MAX_DOT_GRAPH_WIDTH = 1024
-
-# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
-# (in pixels) of the graphs generated by dot. If a graph becomes larger than
-# this value, doxygen will try to truncate the graph, so that it fits within
-# the specified constraint. Beware that most browsers cannot cope with very
-# large images.
-
-MAX_DOT_GRAPH_HEIGHT = 1024
-
-# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
-# generate a legend page explaining the meaning of the various boxes and
-# arrows in the dot generated graphs.
-
-GENERATE_LEGEND = YES
-
-#---------------------------------------------------------------------------
-# Configuration::addtions related to the search engine
-#---------------------------------------------------------------------------
-
-# The SEARCHENGINE tag specifies whether or not a search engine should be
-# used. If set to NO the values of all tags below this one will be ignored.
-
-SEARCHENGINE = NO
-
-# The CGI_NAME tag should be the name of the CGI script that
-# starts the search engine (doxysearch) with the correct parameters.
-# A script with this name will be generated by doxygen.
-
-CGI_NAME = search.cgi
-
-# The CGI_URL tag should be the absolute URL to the directory where the
-# cgi binaries are located. See the documentation of your http daemon for
-# details.
-
-CGI_URL =
-
-# The DOC_URL tag should be the absolute URL to the directory where the
-# documentation is located. If left blank the absolute path to the
-# documentation, with file:// prepended to it, will be used.
-
-DOC_URL =
-
-# The DOC_ABSPATH tag should be the absolute path to the directory where the
-# documentation is located. If left blank the directory on the local machine
-# will be used.
-
-DOC_ABSPATH =
-
-# The BIN_ABSPATH tag must point to the directory where the doxysearch binary
-# is installed.
-
-BIN_ABSPATH = /usr/local/bin/
-
-# The EXT_DOC_PATHS tag can be used to specify one or more paths to
-# documentation generated for other projects. This allows doxysearch to search
-# the documentation for these projects as well.
-
-EXT_DOC_PATHS =
Deleted: rosegarden/branches/upstream/1.2.3/README
===================================================================
--- rosegarden/branches/upstream/1.2.3/README 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/branches/upstream/1.2.3/README 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,182 +0,0 @@
-
-Rosegarden-4 v1.2.3
-===================
-
-Rosegarden-4 is a MIDI and audio sequencer and musical notation editor.
-
-Please keep an eye on the FAQ for known problems and workarounds:
-
- http://www.rosegardenmusic.com/resources/faq/
-
-When you find bugs, first check whether a newer version of Rosegarden
-has been released yet; if not, please continue on to:
-
- http://rosegarden.sourceforge.net/tutorial/bug-guidelines.html
-
-
-Build requirements
-------------------
-
-The big requirement is KDE 3.1, or later, or more specifically the KDE 3.1+
-development libraries (you don't need the whole KDE environment).
-
-Our code compiles with gcc-3.x and gcc-4.x.
-
-For MIDI support on Linux, you need ALSA 0.9.x or 1.0; for audio you
-need JACK 0.77 or newer; for synth plugins you need DSSI 0.9.x or
-newer; for synth plugin GUI support you need liblo 0.7 or newer.
-
-We have recently switched from automake/autoconf/make to scons for
-building. Please see the section on Compiling from Source below for
-details.
-
-
-Compiling from source
----------------------
-
-You will need to obtain and install scons. If you are not familiar with
-scons, it's a more modern alternative to "make". See this page:
-
- http://scons.sourceforge.net/
-
-For a typical end-user installation with no unusual requirements, simply run
-
- scons configure
- scons
- scons install
-
-The build system should automatically detect your installation prefix
-and various optional installed libraries with no further effort on
-your part. It will tell you if something it needs does not appear to
-be available.
-
-For special requirements, a few options are supported. These take the
-format scons configure option=[0|1], for example
-
- scons configure debug=1
-
-To see a list of available options, use
-
- scons configure --help
-
-To perform the equivalent of a "make clean" or "make distclean" use
-
- scons -c
-
-To uninstall, use
-
- scons -c install
-
-NOTE: The installation prefix should be the same as the one of your
-KDE installation. However you can install to another directory, but
-then you'll have to append it to your KDEDIRS variable. For instance :
-
-KDEDIRS=/usr:/home/glaurent/rosegarden
-
-
-Running Rosegarden
-------------------
-
-Just run the "rosegarden" application (found in the KDE bin directory
-after installation). The sequencer process is started automatically
-when the gui is started, provided it has been correctly installed (by
-"make install") in the global KDE directories. If you have any
-problems running the application, consult the FAQ:
-
- http://www.rosegardenmusic.com/resources/faq/
-
-or if that doesn't answer your question then use the rosegarden-user
-mailing list on SourceForge.
-
-You can also "scons -c install" if you decide it's a waste of your time.
-
-
-User documentation
-------------------
-
-There is a lot of documentation for Rosegarden available through the
-Help menu. Go to Help -> Rosegarden Handbook for the reference
-manual, and Help -> Online Tutorial for a tutorial.
-
-
-SPECIAL NOTES FOR PACKAGE MAINTAINERS
--------------------------------------
-
-DSSI
-
-Many distros released their packages of Rosegarden-4 v1.0 compiled
-without the optional DSSI/synth plugin support. We received a lot of
-complaints on our lists from your users and ours about your packages
-being built without this feature.
-
-We would like to request that you please take whatever steps are
-necessary within the framework of your particular distro to ensure
-that Rosegarden is built with DSSI support, and ideally that some of
-the currently available DSSI plugins are also packaged for your
-distro. Thank you. For details on DSSI, see:
-
- http://dssi.sourceforge.net/
-
-
-Notes for developers
---------------------
-
-We are actively seeking developers who are interested in coding new
-parts of the application, adding features, and fixing bugs. See the
-bug and feature request trackers at SourceForge for inspiration. If
-you intend to do anything, please discuss it on the rosegarden-devel
-mailing list (of course, providing working code will make your
-argument extra persuasive).
-
-Be warned that we tend to be fairly strict about code quality... as
-far as that's possible, given the not always superb standards of our
-own code.
-
-
-Developer documentation
------------------------
-
-All the documentation we have (not enough) is in the docs/
-subdirectory, including:
-
- docs/code/global_design.txt -- which classes do what, more or less
- docs/data_struct/units.txt -- how we store pitch and time
- docs/data_struct/sets.txt -- some terminology explained
-
- docs/howtos/alsa-notes -- brief notes about getting and installing the
- ALSA sound drivers (we recommend ALSA for use with Rosegarden)
- docs/howtos/artsd-mcop-notes.txt -- notes on how to get sound with aRts
- (not recommended!)
-
-
-Authors and copyright
----------------------
-
-* Rosegarden-4 is Copyright 2000-2006 Guillaume Laurent, Chris Cannam
- and Richard Bown.
-
-* The moral right of Guillaume Laurent, Chris Cannam and Richard Bown
- to be identified as the authors of this work has been asserted.
-
-* Parts of Rosegarden-4 are derived from Rosegarden 2.1, which is
- Copyright 1994 - 2001 Chris Cannam, Andrew Green, Richard Bown and
- Guillaume Laurent.
-
-* For musical notation display Rosegarden-4 uses pixmaps derived from
- the Feta font, part of the Lilypond software (http://lilypond.org/)
- which is Copyright 1997 - 2004 Jan Nieuwenhuizen and Han-Wen Nienhuys.
-
-* Other major contributors include Randall Farmer, Ron Kuris, Hans
- Kieserman, Michael McIntyre, and Pedro Lopez-Cabanillas. See AUTHORS for
- more details, and the individual source files for copyright attributions.
-
-* The Rosegarden splash-screen image is Copyright 2005 Carolyn H. McIntyre,
- used by permission. (It is a photograph of a rose growing in Michael
- McIntyre's real live rose garden.)
-
-Rosegarden-4 is free software; you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation; either version 2 of the License, or (at
-your option) any later version. See the file COPYING included with
-this distribution for more information.
-
Deleted: rosegarden/branches/upstream/1.2.3/SConstruct
===================================================================
--- rosegarden/branches/upstream/1.2.3/SConstruct 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/branches/upstream/1.2.3/SConstruct 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,243 +0,0 @@
-#!/usr/bin/python
-## scons script for building rosegarden, adapted from
-## the scons script for building the kde test applications
-## by Thomas Nagy, 2004 (bksys)
-##
-## Guillaume Laurent <glaurent at telegraph-road.org>,
-## Chris Cannam <cannam at all-day-breakfast.com>,
-## Richard Bown <bownie at bownie.com>
-## Stephen Torri <storri at torri.org>
-
-"""
-Extract from bksys doc :
-
-To compile the project, you will then only need to launch
-scons on the top-level directory, the scripts find and
-cache the proper environment automatically :
--> scons
-
-To clean the project
--> scons -c
-
-To install the project
--> scons install
-
-To uninstall the project
--> scons -c install
-
-To compile while being in a subdirectory
--> cd src; scons -u
-
-To (re)configure the project and give particular arguments, use ie :
--> scons configure debug=1
--> scons configure prefix=/tmp/ita debug=full extraincludes=/usr/local/include:/tmp/include prefix=/usr/local
-The variables are saved automatically after the first run
-(look at cache/kde.cache.py, ..)
-
-You can alternate between debug/non-debug mode very easily :
-
-scons configure debug=1; scons; scons configure ;
-"""
-
-# Define the version
-VERSION = "4-1.2.3"
-
-import os
-import glob
-import fnmatch
-import re
-import string
-import sys
-
-env = Environment(TARGS=COMMAND_LINE_TARGETS, ARGS=ARGUMENTS,
- tools = ['default', 'generic', 'kde', 'sound', 'test', 'rosegarden'],
- toolpath=['./', 'scons_admin/'])
-
-#-----------------------------
-# Variables
-#-----------------------------
-
-# Setup the default build directory to c_reldir
-c_builddir = 'RGbuild'
-
-## Exit if configuration requested (scons configure)
-if 'configure' in COMMAND_LINE_TARGETS:
- env.Exit(0)
-#-----------------------------
-# Environment
-#-----------------------------
-env.AppendUnique( ENV = os.environ )
-env.AppendUnique( ENV = {'PATH' : os.environ['PATH'], 'HOME' : os.environ['HOME']} )
-
-## Use this to set rpath - this may cause trouble if folders are moved (chrpath)
-env.Append( RPATH = [env['QTLIBPATH'], env['KDELIBPATH'], env['KDEMODULE']] )
-
-# Export 'env' so that sconscripts in subdirectories can use it
-Export( "env" )
-
-## The qt library is needed by every sub-program
-env.AppendUnique(LIBS = ['qt-mt'])
-
-## Threading is needed
-env.Append(CCFLAGS = '-DQT_THREAD_SUPPORT')
-
-env.Append(CCFLAGS = '-DVERSION=\\"' + VERSION + '\\"')
-
-##!!! WTF? This is supposed to be defined if NDEBUG is set, which is supposed
-## to happen if debug is not actively requested
-##env.Append(CCFLAGS = '-DNO_TIMING')
-
-#-----------------------------
-# Build
-#-----------------------------
-def givedir(dir):
- return env.join(c_builddir, dir)
-
-SetOption('duplicate', 'soft-copy')
-dirs = env.Split("""
- sound
- sequencer
- gui
- base
-""")
-
-bdirs=[]
-for d in dirs:
- tmpdir = givedir(d)
- env.BuildDir(tmpdir, d)
- bdirs.append(tmpdir)
-env.subdirs(bdirs)
-
-# disable object cache, unless you want it (define the SCONS_CACHE env. var)
-if not os.environ.has_key('SCONS_CACHE'):
- env.CacheDir(None)
-
-#-----------------------------
-# Process the translations
-#-----------------------------
-
-## They are usually located in the po/ directory
-env.KDElang('po/', 'rosegarden')
-
-
-#-----------------------------
-# Installation
-#-----------------------------
-
-if 'install' in COMMAND_LINE_TARGETS:
-
- # .rc files
- env.KDEinstall('KDEDATA','/rosegarden', glob.glob("gui/*.rc"))
-
- # .desktop file
- env.KDEinstall('KDEMENU','/Applications', 'gui/rosegarden.desktop')
-
- # mime files
- mimefiles = """
- gui/x-rosegarden21.desktop
- gui/x-rosegarden.desktop
- gui/x-rosegarden-device.desktop
- gui/x-soundfont.desktop""".split()
-
- env.KDEinstall('KDEMIME','/audio', mimefiles)
-
- # icons
- env.KDEinstallas('KDEICONS','/locolor/16x16/apps/x-rosegarden.xpm', "gui/pixmaps/icons/cc-hi16-rosegarden.xpm")
- env.KDEinstallas('KDEICONS','/hicolor/16x16/apps/x-rosegarden.xpm', "gui/pixmaps/icons/rg-rwb-rose3-16x16.png")
-
- env.KDEinstallas('KDEICONS','/hicolor/48x48/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-48x48.png")
- env.KDEinstallas('KDEICONS','/hicolor/64x64/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-64x64.png")
-
- env.KDEinstallas('KDEICONS','/hicolor/128x128/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-128x128.png")
-
- env.KDEinstallas('KDEICONS','/locolor/32x32/apps/rosegarden.xpm', "gui/pixmaps/icons/cc-hi32-rosegarden.xpm")
- env.KDEinstallas('KDEICONS','/hicolor/32x32/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-32x32.png")
-
- env.KDEinstallas('KDEICONS','/hicolor/16x16/mimetypes/x-rosegarden.png', "gui/pixmaps/icons/mm-mime-hi16-rosegarden.png")
- env.KDEinstallas('KDEICONS','/locolor/16x16/mimetypes/x-rosegarden.png', "gui/pixmaps/icons/mm-mime-hi16-rosegarden.png")
-
- env.KDEinstallas('KDEICONS','/hicolor/32x32/mimetypes/x-rosegarden.png', "gui/pixmaps/icons/mm-mime-hi32-rosegarden.png")
- env.KDEinstallas('KDEICONS','/locolor/32x32/mimetypes/x-rosegarden.png', "gui/pixmaps/icons/mm-mime-hi32-rosegarden.png")
-
- # styles
- #for s in glob.glob("gui/styles/*.xml"):
- env.KDEinstall('KDEDATA','/rosegarden/styles', glob.glob("gui/styles/*.xml"))
-
- # fonts
- #for s in glob.glob("gui/fonts/*.pfa"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts', glob.glob("gui/fonts/*.pfa"))
-
- #for s in glob.glob("gui/fonts/mappings/*.xml"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/mappings',glob.glob("gui/fonts/mappings/*.xml"))
-
- #for s in glob.glob("gui/pixmaps/rg21/4/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/rg21/4', glob.glob("gui/pixmaps/rg21/4/*.xpm"))
- #for s in glob.glob("gui/pixmaps/rg21/8/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/rg21/8', glob.glob("gui/pixmaps/rg21/8/*.xpm"))
-
- #for s in glob.glob("gui/pixmaps/feta/4/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/4', glob.glob("gui/pixmaps/feta/4/*.xpm"))
- #for s in glob.glob("gui/pixmaps/feta/6/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/6', glob.glob("gui/pixmaps/feta/6/*.xpm"))
- #for s in glob.glob("gui/pixmaps/feta/8/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/8', glob.glob("gui/pixmaps/feta/8/*.xpm"))
- #for s in glob.glob("gui/pixmaps/feta/10/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/10', glob.glob("gui/pixmaps/feta/10/*.xpm"))
- #for s in glob.glob("gui/pixmaps/feta/12/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/12', glob.glob("gui/pixmaps/feta/12/*.xpm"))
-
- # pixmaps
- #for s in glob.glob("gui/pixmaps/misc/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/misc', glob.glob("gui/pixmaps/misc/*.xpm"))
-
- #for s in glob.glob("gui/pixmaps/toolbar/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/toolbar', glob.glob("gui/pixmaps/toolbar/*.xpm"))
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/toolbar', glob.glob("gui/pixmaps/toolbar/*.png"))
-
- #for s in glob.glob("gui/pixmaps/transport/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/transport', glob.glob("gui/pixmaps/transport/*.xpm"))
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/transport', glob.glob("gui/pixmaps/transport/*.png"))
-
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps', "gui/pixmaps/splash.png")
-
-
- # examples
- examples="""
- gui/testfiles/glazunov.rg
- gui/testfiles/notation-for-string-orchestra-in-D-minor.rg
- gui/testfiles/ravel-pc-gmaj-adagio.rg
- gui/testfiles/perfect-moment.rg
- gui/testfiles/bwv-1060-brass-band-1-allegro.rg
- gui/testfiles/bogus-surf-jam.rg
- gui/testfiles/the-rose-garden.rg
- gui/testfiles/children.rg
- gui/testfiles/stormy-riders.rg
- gui/testfiles/Djer-Fire.rg""".split()
-
- #for ex in examples:
- env.KDEinstall('KDEDATA','/rosegarden/examples', examples)
-
- # autoload.rg
- env.KDEinstall('KDEDATA', '/rosegarden', "gui/testfiles/autoload.rg")
-
- # tips
- env.KDEinstall('KDEDATA', '/rosegarden', "gui/docs/en/tips")
-
- # library files
- #for l in glob.glob("gui/library/*.rgd"):
- env.KDEinstall('KDEDATA', '/rosegarden/library', glob.glob("gui/library/*.rgd"))
-
- # rosegarden-project-package script
- env.KDEinstall('KDEBIN', '', "gui/rosegarden-project-package" )
-
- # rosegarden-lilypondview script
- env.KDEinstall('KDEBIN', '', "gui/rosegarden-lilypondview" )
-
- # version.txt file
- versionFile = open("version.txt", "w")
- versionFile.write(VERSION + '\n')
- versionFile.close()
- env.KDEinstall('KDEDATA', '/rosegarden', "version.txt")
-
-env.dist('rosegarden', VERSION)
-
Deleted: rosegarden/branches/upstream/1.2.3/TRANSLATORS
===================================================================
--- rosegarden/branches/upstream/1.2.3/TRANSLATORS 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/branches/upstream/1.2.3/TRANSLATORS 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,4 +0,0 @@
-Please see the AUTHORS file for a list of translators.
-
-If you'd like to translate Rosegarden into your language, contact us at
-<rosegarden-devel at lists.sourceforge.net>
Deleted: rosegarden/branches/upstream/1.2.3/rosegarden.lsm
===================================================================
--- rosegarden/branches/upstream/1.2.3/rosegarden.lsm 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/branches/upstream/1.2.3/rosegarden.lsm 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,14 +0,0 @@
-Begin3
-Title: Rosegarden-4
-Version: 1.2.3
-Entered-date:
-Description: MIDI and audio sequencer and musical notation editor
-Keywords: KDE Qt JACK ALSA
-Author: Guillaume Laurent <glaurent at telegraph-road.org>, Chris Cannam <cannam at all-day-breakfast.com>, Richard Bown <bownie at bownie.com>
-Maintained-by: Guillaume Laurent <glaurent at telegraph-road.org>, Chris Cannam <cannam at all-day-breakfast.com>, Richard Bown <bownie at bownie.com>
-Home-page: http://www.rosegardenmusic.com/
-Alternate-site:
-Primary-site:
-Platform: Linux
-Copying-policy: GPL
-End
Deleted: rosegarden/trunk/AUTHORS
===================================================================
--- rosegarden/trunk/AUTHORS 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/AUTHORS 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,112 +0,0 @@
-Lead developers:
-
-Chris Cannam <cannam at all-day-breakfast.com>
-Richard Bown <bownie at bownie.com>
-Guillaume Laurent <glaurent at telegraph-road.org>
-
-Adjunct developers:
-
-D. Michael McIntyre <dmmcintyr at users.sourceforge.net>
-
-
-Contributors:
-
-Ron Kuris <rk at prefer.net>
- * cleanups
-
-Randall Farmer <rfarme at simons-rock.edu>
- * chord labelling code
-
-Hans Kieserman <hkieserman at mail.com>
- * Lilypond output
- * assorted other patches
- * i18n-ization
-
-Levi Burton <donburton at sbcglobal.net>
- * UI improvements
- * other bug fixes
-
-Mark Hymers <markh at linuxfromscratch.org>
- * Segment colours
- * Other UI and bug fixes
-
-Alexandre Prokoudine <alexandre.prokoudine at gmail.com>
- * Russian translation
- * i18n-ization
-
-Pedro Lopez-Cabanillas <plcl at users.sourceforge.net>
- * Spanish translation
- * ALSA hacking and bug fixes
- * multi-input MIDI recording
-
-Jörg Schumann <jrschumann at gmx.de>
-Eckhard Jokisch <e.jokisch at u-code.de>
- * German translation
-
-Kevin Donnelly
- * Welsh translation
-
-Didier Burli
- * French translation
-
-Daniele Medri
-Alessandro Musesti
- * Italian translation
-
-Stefan Asserh�l
-Erik Magnus Johansson
- * Swedish translation
-
-Hasso Tepper
- * Estonian translation
-
-Jelmer Vernooij
- * Dutch translation
-
-Oota Toshiya
- * Japanese translation
-
-Kevin Liang
- * HSpinBox class
-
-Thorsten Wilms
- * Original designs on which the Rosegarden rotary controllers are based
-
-William <rosegarden4c AT orthoset.com>
- * auto-scroll deceleration
- * glyphs for rests outside staves and other bug fixes
-
-Liu Songhe <jackliu9999 AT msn.com>
- * Simplified Chinese translation
-
-Thomas Nagy <tnagy256 at yahoo.fr>
- * SCons/bksys building system
-
-Vince Negri <vince-rg at bulbous.freeserve.co.uk>
- * Initial MTC slave implementation (the bits without the bugs)
-
-Toni Arnold <toni__arnold at bluewin.ch>
- * LIRC infrared remote-controller support
-
-Jan B�a <jbina at sky.cz>
- * Czech translation
-
-Vladimir Savic <vladimir at vladimirsavic.net>
- * icons, icons, icons
-
-Lisandro Damián Nicanor Pérez Meyer <perezmeyer at infovia.com.ar>
-Javier Castrillo <riverplatense at gmail.com>
-Lucas Godoy <godoy.lucas at gmail.com>
-Marcos Guglielmetti <marcospcmusica at yahoo.com.ar>
- * Spanish translation
-
-Feliu Ferrer <mverge2 at pie.xtec.es>
-Quim Perez i Noguer <noguer at osona.com>
- * Catalan translation
-
-Carolyn McIntyre <catma at adelphia.net>
- * new splash screen photo (of Michael McIntyre's rose garden)
-
-##
-## Names in here should also be credited in gui/main.cpp, with aboutData.addCredit()
-##
Deleted: rosegarden/trunk/COPYING
===================================================================
--- rosegarden/trunk/COPYING 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/COPYING 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,280 +0,0 @@
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 675 Mass Ave, Cambridge, MA 02139, USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
Deleted: rosegarden/trunk/Doxyfile
===================================================================
--- rosegarden/trunk/Doxyfile 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/Doxyfile 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,753 +0,0 @@
-# Doxyfile 1.2.5
-
-# This file describes the settings to be used by doxygen for a project
-#
-# All text after a hash (#) is considered a comment and will be ignored
-# The format is:
-# TAG = value [value, ...]
-# For lists items can also be appended using:
-# TAG += value [value, ...]
-# Values that contain spaces should be placed between quotes (" ")
-
-#---------------------------------------------------------------------------
-# General configuration options
-#---------------------------------------------------------------------------
-
-# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
-# by quotes) that should identify the project.
-
-PROJECT_NAME = Rosegarden
-
-# The PROJECT_NUMBER tag can be used to enter a project or revision number.
-# This could be handy for archiving the generated documentation or
-# if some version control system is used.
-
-PROJECT_NUMBER = 0.1
-
-# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
-# base path where the generated documentation will be put.
-# If a relative path is entered, it will be relative to the location
-# where doxygen was started. If left blank the current directory will be used.
-
-OUTPUT_DIRECTORY = docs/doxygen
-
-# The OUTPUT_LANGUAGE tag is used to specify the language in which all
-# documentation generated by doxygen is written. Doxygen will use this
-# information to generate all constant output in the proper language.
-# The default language is English, other supported languages are:
-# Dutch, French, Italian, Czech, Swedish, German, Finnish, Japanese,
-# Korean, Hungarian, Norwegian, Spanish, Romanian, Russian, Croatian,
-# Polish, Portuguese and Slovene.
-
-OUTPUT_LANGUAGE = English
-
-# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
-# documentation are documented, even if no documentation was available.
-# Private class members and static file members will be hidden unless
-# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
-
-EXTRACT_ALL = YES
-
-# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
-# will be included in the documentation.
-
-EXTRACT_PRIVATE = NO
-
-# If the EXTRACT_STATIC tag is set to YES all static members of a file
-# will be included in the documentation.
-
-EXTRACT_STATIC = NO
-
-# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
-# undocumented members of documented classes, files or namespaces.
-# If set to NO (the default) these members will be included in the
-# various overviews, but no documentation section is generated.
-# This option has no effect if EXTRACT_ALL is enabled.
-
-HIDE_UNDOC_MEMBERS = NO
-
-# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
-# undocumented classes that are normally visible in the class hierarchy.
-# If set to NO (the default) these class will be included in the various
-# overviews. This option has no effect if EXTRACT_ALL is enabled.
-
-HIDE_UNDOC_CLASSES = NO
-
-# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
-# include brief member descriptions after the members that are listed in
-# the file and class documentation (similar to JavaDoc).
-# Set to NO to disable this.
-
-BRIEF_MEMBER_DESC = YES
-
-# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
-# the brief description of a member or function before the detailed description.
-# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
-# brief descriptions will be completely suppressed.
-
-REPEAT_BRIEF = YES
-
-# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
-# Doxygen will generate a detailed section even if there is only a brief
-# description.
-
-ALWAYS_DETAILED_SEC = NO
-
-# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
-# path before files name in the file list and in the header files. If set
-# to NO the shortest path that makes the file name unique will be used.
-
-FULL_PATH_NAMES = NO
-
-# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
-# can be used to strip a user defined part of the path. Stripping is
-# only done if one of the specified strings matches the left-hand part of
-# the path. It is allowed to use relative paths in the argument list.
-
-STRIP_FROM_PATH =
-
-# The INTERNAL_DOCS tag determines if documentation
-# that is typed after a \internal command is included. If the tag is set
-# to NO (the default) then the documentation will be excluded.
-# Set it to YES to include the internal documentation.
-
-INTERNAL_DOCS = NO
-
-# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
-# generate a class diagram (in Html and LaTeX) for classes with base or
-# super classes. Setting the tag to NO turns the diagrams off.
-
-CLASS_DIAGRAMS = YES
-
-# If the SOURCE_BROWSER tag is set to YES then a list of source files will
-# be generated. Documented entities will be cross-referenced with these sources.
-
-SOURCE_BROWSER = NO
-
-# Setting the INLINE_SOURCES tag to YES will include the body
-# of functions and classes directly in the documentation.
-
-INLINE_SOURCES = NO
-
-# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
-# doxygen to hide any special comment blocks from generated source code
-# fragments. Normal C and C++ comments will always remain visible.
-
-STRIP_CODE_COMMENTS = YES
-
-# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
-# file names in lower case letters. If set to YES upper case letters are also
-# allowed. This is useful if you have classes or files whose names only differ
-# in case and if your file system supports case sensitive file names. Windows
-# users are adviced to set this option to NO.
-
-CASE_SENSE_NAMES = YES
-
-# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
-# will show members with their full class and namespace scopes in the
-# documentation. If set to YES the scope will be hidden.
-
-HIDE_SCOPE_NAMES = NO
-
-# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
-# will generate a verbatim copy of the header file for each class for
-# which an include is specified. Set to NO to disable this.
-
-VERBATIM_HEADERS = YES
-
-# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
-# will put list of the files that are included by a file in the documentation
-# of that file.
-
-SHOW_INCLUDE_FILES = YES
-
-# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
-# will interpret the first line (until the first dot) of a JavaDoc-style
-# comment as the brief description. If set to NO, the JavaDoc
-# comments will behave just like the Qt-style comments (thus requiring an
-# explict @brief command for a brief description.
-
-JAVADOC_AUTOBRIEF = NO
-
-# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
-# member inherits the documentation from any documented member that it
-# reimplements.
-
-INHERIT_DOCS = YES
-
-# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
-# is inserted in the documentation for inline members.
-
-INLINE_INFO = YES
-
-# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
-# will sort the (detailed) documentation of file and class members
-# alphabetically by member name. If set to NO the members will appear in
-# declaration order.
-
-SORT_MEMBER_DOCS = YES
-
-# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
-# tag is set to YES, then doxygen will reuse the documentation of the first
-# member in the group (if any) for the other members of the group. By default
-# all members of a group must be documented explicitly.
-
-DISTRIBUTE_GROUP_DOC = NO
-
-# The TAB_SIZE tag can be used to set the number of spaces in a tab.
-# Doxygen uses this value to replace tabs by spaces in code fragments.
-
-TAB_SIZE = 8
-
-# The ENABLE_SECTIONS tag can be used to enable conditional
-# documentation sections, marked by \if sectionname ... \endif.
-
-ENABLED_SECTIONS =
-
-# The GENERATE_TODOLIST tag can be used to enable (YES) or
-# disable (NO) the todo list. This list is created by putting \todo
-# commands in the documentation.
-
-GENERATE_TODOLIST = YES
-
-# The GENERATE_TESTLIST tag can be used to enable (YES) or
-# disable (NO) the test list. This list is created by putting \test
-# commands in the documentation.
-
-GENERATE_TESTLIST = YES
-
-# This tag can be used to specify a number of aliases that acts
-# as commands in the documentation. An alias has the form "name=value".
-# For example adding "sideeffect=\par Side Effects:\n" will allow you to
-# put the command \sideeffect (or @sideeffect) in the documentation, which
-# will result in a user defined paragraph with heading "Side Effects:".
-# You can put \n's in the value part of an alias to insert newlines.
-
-ALIASES =
-
-# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
-# the initial value of a variable or define consist of for it to appear in
-# the documentation. If the initializer consists of more lines than specified
-# here it will be hidden. Use a value of 0 to hide initializers completely.
-# The appearance of the initializer of individual variables and defines in the
-# documentation can be controlled using \showinitializer or \hideinitializer
-# command in the documentation regardless of this setting.
-
-MAX_INITIALIZER_LINES = 30
-
-# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
-# only. Doxygen will then generate output that is more tailored for C.
-# For instance some of the names that are used will be different. The list
-# of all members will be omitted, etc.
-
-OPTIMIZE_OUTPUT_FOR_C = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to warning and progress messages
-#---------------------------------------------------------------------------
-
-# The QUIET tag can be used to turn on/off the messages that are generated
-# by doxygen. Possible values are YES and NO. If left blank NO is used.
-
-QUIET = NO
-
-# The WARNINGS tag can be used to turn on/off the warning messages that are
-# generated by doxygen. Possible values are YES and NO. If left blank
-# NO is used.
-
-WARNINGS = YES
-
-# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
-# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
-# automatically be disabled.
-
-WARN_IF_UNDOCUMENTED = YES
-
-# The WARN_FORMAT tag determines the format of the warning messages that
-# doxygen can produce. The string should contain the $file, $line, and $text
-# tags, which will be replaced by the file and line number from which the
-# warning originated and the warning text.
-
-WARN_FORMAT = "$file:$line: $text"
-
-# The WARN_LOGFILE tag can be used to specify a file to which warning
-# and error messages should be written. If left blank the output is written
-# to stderr.
-
-WARN_LOGFILE =
-
-#---------------------------------------------------------------------------
-# configuration options related to the input files
-#---------------------------------------------------------------------------
-
-# The INPUT tag can be used to specify the files and/or directories that contain
-# documented source files. You may enter file names like "myfile.cpp" or
-# directories like "/usr/src/myproject". Separate the files or directories
-# with spaces.
-
-INPUT = base sound sequencer gui
-#INPUT = gui/main.cpp
-
-# If the value of the INPUT tag contains directories, you can use the
-# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
-# and *.h) to filter out the source-files in the directories. If left
-# blank all files are included.
-
-FILE_PATTERNS = *.h *.C *.cpp *.cc
-
-# The RECURSIVE tag can be used to turn specify whether or not subdirectories
-# should be searched for input files as well. Possible values are YES and NO.
-# If left blank NO is used.
-
-RECURSIVE = NO
-
-# The EXCLUDE tag can be used to specify files and/or directories that should
-# excluded from the INPUT source files. This way you can easily exclude a
-# subdirectory from a directory tree whose root is specified with the INPUT tag.
-
-EXCLUDE =
-
-# If the value of the INPUT tag contains directories, you can use the
-# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
-# certain files from those directories.
-
-EXCLUDE_PATTERNS = *.moc.cpp *_skel.cpp
-
-# The EXAMPLE_PATH tag can be used to specify one or more files or
-# directories that contain example code fragments that are included (see
-# the \include command).
-
-EXAMPLE_PATH =
-
-# If the value of the EXAMPLE_PATH tag contains directories, you can use the
-# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
-# and *.h) to filter out the source-files in the directories. If left
-# blank all files are included.
-
-EXAMPLE_PATTERNS =
-
-# The IMAGE_PATH tag can be used to specify one or more files or
-# directories that contain image that are included in the documentation (see
-# the \image command).
-
-IMAGE_PATH =
-
-# The INPUT_FILTER tag can be used to specify a program that doxygen should
-# invoke to filter for each input file. Doxygen will invoke the filter program
-# by executing (via popen()) the command <filter> <input-file>, where <filter>
-# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
-# input file. Doxygen will then use the output that the filter program writes
-# to standard output.
-
-INPUT_FILTER =
-
-# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
-# INPUT_FILTER) will be used to filter the input files when producing source
-# files to browse.
-
-FILTER_SOURCE_FILES = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the alphabetical class index
-#---------------------------------------------------------------------------
-
-# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
-# of all compounds will be generated. Enable this if the project
-# contains a lot of classes, structs, unions or interfaces.
-
-ALPHABETICAL_INDEX = NO
-
-# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
-# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
-# in which this list will be split (can be a number in the range [1..20])
-
-COLS_IN_ALPHA_INDEX = 5
-
-# In case all classes in a project start with a common prefix, all
-# classes will be put under the same header in the alphabetical index.
-# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
-# should be ignored while generating the index headers.
-
-IGNORE_PREFIX =
-
-#---------------------------------------------------------------------------
-# configuration options related to the HTML output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
-# generate HTML output.
-
-GENERATE_HTML = YES
-
-# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `html' will be used as the default path.
-
-HTML_OUTPUT = html
-
-# The HTML_HEADER tag can be used to specify a personal HTML header for
-# each generated HTML page. If it is left blank doxygen will generate a
-# standard header.
-
-HTML_HEADER =
-
-# The HTML_FOOTER tag can be used to specify a personal HTML footer for
-# each generated HTML page. If it is left blank doxygen will generate a
-# standard footer.
-
-HTML_FOOTER =
-
-# The HTML_STYLESHEET tag can be used to specify a user defined cascading
-# style sheet that is used by each HTML page. It can be used to
-# fine-tune the look of the HTML output. If the tag is left blank doxygen
-# will generate a default style sheet
-
-HTML_STYLESHEET =
-
-# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
-# files or namespaces will be aligned in HTML using tables. If set to
-# NO a bullet list will be used.
-
-HTML_ALIGN_MEMBERS = YES
-
-# If the GENERATE_HTMLHELP tag is set to YES, additional index files
-# will be generated that can be used as input for tools like the
-# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
-# of the generated HTML documentation.
-
-GENERATE_HTMLHELP = NO
-
-# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
-# top of each HTML page. The value NO (the default) enables the index and
-# the value YES disables it.
-
-DISABLE_INDEX = NO
-
-# This tag can be used to set the number of enum values (range [1..20])
-# that doxygen will group on one line in the generated HTML documentation.
-
-ENUM_VALUES_PER_LINE = 4
-
-# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
-# generated containing a tree-like index structure (just like the one that
-# is generated for HTML Help). For this to work a browser that supports
-# JavaScript and frames is required (for instance Netscape 4.0+
-# or Internet explorer 4.0+).
-
-GENERATE_TREEVIEW = NO
-
-# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
-# used to set the initial width (in pixels) of the frame in which the tree
-# is shown.
-
-TREEVIEW_WIDTH = 250
-
-#---------------------------------------------------------------------------
-# configuration options related to the LaTeX output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
-# generate Latex output.
-
-GENERATE_LATEX = NO
-
-# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `latex' will be used as the default path.
-
-LATEX_OUTPUT = latex
-
-# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
-# LaTeX documents. This may be useful for small projects and may help to
-# save some trees in general.
-
-COMPACT_LATEX = NO
-
-# The PAPER_TYPE tag can be used to set the paper type that is used
-# by the printer. Possible values are: a4, a4wide, letter, legal and
-# executive. If left blank a4wide will be used.
-
-PAPER_TYPE = a4wide
-
-# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
-# packages that should be included in the LaTeX output.
-
-EXTRA_PACKAGES =
-
-# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
-# the generated latex document. The header should contain everything until
-# the first chapter. If it is left blank doxygen will generate a
-# standard header. Notice: only use this tag if you know what you are doing!
-
-LATEX_HEADER =
-
-# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
-# is prepared for conversion to pdf (using ps2pdf). The pdf file will
-# contain links (just like the HTML output) instead of page references
-# This makes the output suitable for online browsing using a pdf viewer.
-
-PDF_HYPERLINKS = NO
-
-# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
-# plain latex in the generated Makefile. Set this option to YES to get a
-# higher quality PDF documentation.
-
-USE_PDFLATEX = NO
-
-# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
-# command to the generated LaTeX files. This will instruct LaTeX to keep
-# running if errors occur, instead of asking the user for help.
-# This option is also used when generating formulas in HTML.
-
-LATEX_BATCHMODE = NO
-
-#---------------------------------------------------------------------------
-# configuration options related to the RTF output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
-# The RTF output is optimised for Word 97 and may not look very pretty with
-# other RTF readers or editors.
-
-GENERATE_RTF = NO
-
-# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `rtf' will be used as the default path.
-
-RTF_OUTPUT = rtf
-
-# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
-# RTF documents. This may be useful for small projects and may help to
-# save some trees in general.
-
-COMPACT_RTF = NO
-
-# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
-# will contain hyperlink fields. The RTF file will
-# contain links (just like the HTML output) instead of page references.
-# This makes the output suitable for online browsing using a WORD or other.
-# programs which support those fields.
-# Note: wordpad (write) and others do not support links.
-
-RTF_HYPERLINKS = NO
-
-# Load stylesheet definitions from file. Syntax is similar to doxygen's
-# config file, i.e. a series of assigments. You only have to provide
-# replacements, missing definitions are set to their default value.
-
-RTF_STYLESHEET_FILE =
-
-#---------------------------------------------------------------------------
-# configuration options related to the man page output
-#---------------------------------------------------------------------------
-
-# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
-# generate man pages
-
-GENERATE_MAN = NO
-
-# The MAN_OUTPUT tag is used to specify where the man pages will be put.
-# If a relative path is entered the value of OUTPUT_DIRECTORY will be
-# put in front of it. If left blank `man' will be used as the default path.
-
-MAN_OUTPUT = man
-
-# The MAN_EXTENSION tag determines the extension that is added to
-# the generated man pages (default is the subroutine's section .3)
-
-MAN_EXTENSION = .3
-
-#---------------------------------------------------------------------------
-# Configuration options related to the preprocessor
-#---------------------------------------------------------------------------
-
-# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
-# evaluate all C-preprocessor directives found in the sources and include
-# files.
-
-ENABLE_PREPROCESSING = YES
-
-# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
-# names in the source code. If set to NO (the default) only conditional
-# compilation will be performed. Macro expansion can be done in a controlled
-# way by setting EXPAND_ONLY_PREDEF to YES.
-
-MACRO_EXPANSION = NO
-
-# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
-# then the macro expansion is limited to the macros specified with the
-# PREDEFINED and EXPAND_AS_PREDEFINED tags.
-
-EXPAND_ONLY_PREDEF = NO
-
-# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
-# in the INCLUDE_PATH (see below) will be search if a #include is found.
-
-SEARCH_INCLUDES = YES
-
-# The INCLUDE_PATH tag can be used to specify one or more directories that
-# contain include files that are not input files but should be processed by
-# the preprocessor.
-
-INCLUDE_PATH =
-
-# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
-# patterns (like *.h and *.hpp) to filter out the header-files in the
-# directories. If left blank, the patterns specified with FILE_PATTERNS will
-# be used.
-
-INCLUDE_FILE_PATTERNS =
-
-# The PREDEFINED tag can be used to specify one or more macro names that
-# are defined before the preprocessor is started (similar to the -D option of
-# gcc). The argument of the tag is a list of macros of the form: name
-# or name=definition (no spaces). If the definition and the = are
-# omitted =1 is assumed.
-
-PREDEFINED =
-
-# If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
-# this tag can be used to specify a list of macro names that should be expanded.
-# The macro definition that is found in the sources will be used.
-# Use the PREDEFINED tag if you want to use a different macro definition.
-
-EXPAND_AS_DEFINED =
-
-#---------------------------------------------------------------------------
-# Configuration::addtions related to external references
-#---------------------------------------------------------------------------
-
-# The TAGFILES tag can be used to specify one or more tagfiles.
-
-TAGFILES =
-
-# When a file name is specified after GENERATE_TAGFILE, doxygen will create
-# a tag file that is based on the input files it reads.
-
-GENERATE_TAGFILE =
-
-# If the ALLEXTERNALS tag is set to YES all external classes will be listed
-# in the class index. If set to NO only the inherited external classes
-# will be listed.
-
-ALLEXTERNALS = NO
-
-# The PERL_PATH should be the absolute path and name of the perl script
-# interpreter (i.e. the result of `which perl').
-
-PERL_PATH = /usr/bin/perl
-
-#---------------------------------------------------------------------------
-# Configuration options related to the dot tool
-#---------------------------------------------------------------------------
-
-# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
-# available from the path. This tool is part of Graphviz, a graph visualization
-# toolkit from AT&T and Lucent Bell Labs. The other options in this section
-# have no effect if this option is set to NO (the default)
-
-HAVE_DOT = NO
-
-# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
-# will generate a graph for each documented class showing the direct and
-# indirect inheritance relations. Setting this tag to YES will force the
-# the CLASS_DIAGRAMS tag to NO.
-
-CLASS_GRAPH = YES
-
-# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
-# will generate a graph for each documented class showing the direct and
-# indirect implementation dependencies (inheritance, containment, and
-# class references variables) of the class with other documented classes.
-
-COLLABORATION_GRAPH = YES
-
-# If the ENABLE_PREPROCESSING, INCLUDE_GRAPH, and HAVE_DOT tags are set to
-# YES then doxygen will generate a graph for each documented file showing
-# the direct and indirect include dependencies of the file with other
-# documented files.
-
-INCLUDE_GRAPH = YES
-
-# If the ENABLE_PREPROCESSING, INCLUDED_BY_GRAPH, and HAVE_DOT tags are set to
-# YES then doxygen will generate a graph for each documented header file showing
-# the documented files that directly or indirectly include this file
-
-INCLUDED_BY_GRAPH = YES
-
-# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
-# will graphical hierarchy of all classes instead of a textual one.
-
-GRAPHICAL_HIERARCHY = YES
-
-# The tag DOT_PATH can be used to specify the path where the dot tool can be
-# found. If left blank, it is assumed the dot tool can be found on the path.
-
-DOT_PATH =
-
-# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
-# (in pixels) of the graphs generated by dot. If a graph becomes larger than
-# this value, doxygen will try to truncate the graph, so that it fits within
-# the specified constraint. Beware that most browsers cannot cope with very
-# large images.
-
-MAX_DOT_GRAPH_WIDTH = 1024
-
-# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
-# (in pixels) of the graphs generated by dot. If a graph becomes larger than
-# this value, doxygen will try to truncate the graph, so that it fits within
-# the specified constraint. Beware that most browsers cannot cope with very
-# large images.
-
-MAX_DOT_GRAPH_HEIGHT = 1024
-
-# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
-# generate a legend page explaining the meaning of the various boxes and
-# arrows in the dot generated graphs.
-
-GENERATE_LEGEND = YES
-
-#---------------------------------------------------------------------------
-# Configuration::addtions related to the search engine
-#---------------------------------------------------------------------------
-
-# The SEARCHENGINE tag specifies whether or not a search engine should be
-# used. If set to NO the values of all tags below this one will be ignored.
-
-SEARCHENGINE = NO
-
-# The CGI_NAME tag should be the name of the CGI script that
-# starts the search engine (doxysearch) with the correct parameters.
-# A script with this name will be generated by doxygen.
-
-CGI_NAME = search.cgi
-
-# The CGI_URL tag should be the absolute URL to the directory where the
-# cgi binaries are located. See the documentation of your http daemon for
-# details.
-
-CGI_URL =
-
-# The DOC_URL tag should be the absolute URL to the directory where the
-# documentation is located. If left blank the absolute path to the
-# documentation, with file:// prepended to it, will be used.
-
-DOC_URL =
-
-# The DOC_ABSPATH tag should be the absolute path to the directory where the
-# documentation is located. If left blank the directory on the local machine
-# will be used.
-
-DOC_ABSPATH =
-
-# The BIN_ABSPATH tag must point to the directory where the doxysearch binary
-# is installed.
-
-BIN_ABSPATH = /usr/local/bin/
-
-# The EXT_DOC_PATHS tag can be used to specify one or more paths to
-# documentation generated for other projects. This allows doxysearch to search
-# the documentation for these projects as well.
-
-EXT_DOC_PATHS =
Deleted: rosegarden/trunk/README
===================================================================
--- rosegarden/trunk/README 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/README 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,182 +0,0 @@
-
-Rosegarden-4 v1.2.3
-===================
-
-Rosegarden-4 is a MIDI and audio sequencer and musical notation editor.
-
-Please keep an eye on the FAQ for known problems and workarounds:
-
- http://www.rosegardenmusic.com/resources/faq/
-
-When you find bugs, first check whether a newer version of Rosegarden
-has been released yet; if not, please continue on to:
-
- http://rosegarden.sourceforge.net/tutorial/bug-guidelines.html
-
-
-Build requirements
-------------------
-
-The big requirement is KDE 3.1, or later, or more specifically the KDE 3.1+
-development libraries (you don't need the whole KDE environment).
-
-Our code compiles with gcc-3.x and gcc-4.x.
-
-For MIDI support on Linux, you need ALSA 0.9.x or 1.0; for audio you
-need JACK 0.77 or newer; for synth plugins you need DSSI 0.9.x or
-newer; for synth plugin GUI support you need liblo 0.7 or newer.
-
-We have recently switched from automake/autoconf/make to scons for
-building. Please see the section on Compiling from Source below for
-details.
-
-
-Compiling from source
----------------------
-
-You will need to obtain and install scons. If you are not familiar with
-scons, it's a more modern alternative to "make". See this page:
-
- http://scons.sourceforge.net/
-
-For a typical end-user installation with no unusual requirements, simply run
-
- scons configure
- scons
- scons install
-
-The build system should automatically detect your installation prefix
-and various optional installed libraries with no further effort on
-your part. It will tell you if something it needs does not appear to
-be available.
-
-For special requirements, a few options are supported. These take the
-format scons configure option=[0|1], for example
-
- scons configure debug=1
-
-To see a list of available options, use
-
- scons configure --help
-
-To perform the equivalent of a "make clean" or "make distclean" use
-
- scons -c
-
-To uninstall, use
-
- scons -c install
-
-NOTE: The installation prefix should be the same as the one of your
-KDE installation. However you can install to another directory, but
-then you'll have to append it to your KDEDIRS variable. For instance :
-
-KDEDIRS=/usr:/home/glaurent/rosegarden
-
-
-Running Rosegarden
-------------------
-
-Just run the "rosegarden" application (found in the KDE bin directory
-after installation). The sequencer process is started automatically
-when the gui is started, provided it has been correctly installed (by
-"make install") in the global KDE directories. If you have any
-problems running the application, consult the FAQ:
-
- http://www.rosegardenmusic.com/resources/faq/
-
-or if that doesn't answer your question then use the rosegarden-user
-mailing list on SourceForge.
-
-You can also "scons -c install" if you decide it's a waste of your time.
-
-
-User documentation
-------------------
-
-There is a lot of documentation for Rosegarden available through the
-Help menu. Go to Help -> Rosegarden Handbook for the reference
-manual, and Help -> Online Tutorial for a tutorial.
-
-
-SPECIAL NOTES FOR PACKAGE MAINTAINERS
--------------------------------------
-
-DSSI
-
-Many distros released their packages of Rosegarden-4 v1.0 compiled
-without the optional DSSI/synth plugin support. We received a lot of
-complaints on our lists from your users and ours about your packages
-being built without this feature.
-
-We would like to request that you please take whatever steps are
-necessary within the framework of your particular distro to ensure
-that Rosegarden is built with DSSI support, and ideally that some of
-the currently available DSSI plugins are also packaged for your
-distro. Thank you. For details on DSSI, see:
-
- http://dssi.sourceforge.net/
-
-
-Notes for developers
---------------------
-
-We are actively seeking developers who are interested in coding new
-parts of the application, adding features, and fixing bugs. See the
-bug and feature request trackers at SourceForge for inspiration. If
-you intend to do anything, please discuss it on the rosegarden-devel
-mailing list (of course, providing working code will make your
-argument extra persuasive).
-
-Be warned that we tend to be fairly strict about code quality... as
-far as that's possible, given the not always superb standards of our
-own code.
-
-
-Developer documentation
------------------------
-
-All the documentation we have (not enough) is in the docs/
-subdirectory, including:
-
- docs/code/global_design.txt -- which classes do what, more or less
- docs/data_struct/units.txt -- how we store pitch and time
- docs/data_struct/sets.txt -- some terminology explained
-
- docs/howtos/alsa-notes -- brief notes about getting and installing the
- ALSA sound drivers (we recommend ALSA for use with Rosegarden)
- docs/howtos/artsd-mcop-notes.txt -- notes on how to get sound with aRts
- (not recommended!)
-
-
-Authors and copyright
----------------------
-
-* Rosegarden-4 is Copyright 2000-2006 Guillaume Laurent, Chris Cannam
- and Richard Bown.
-
-* The moral right of Guillaume Laurent, Chris Cannam and Richard Bown
- to be identified as the authors of this work has been asserted.
-
-* Parts of Rosegarden-4 are derived from Rosegarden 2.1, which is
- Copyright 1994 - 2001 Chris Cannam, Andrew Green, Richard Bown and
- Guillaume Laurent.
-
-* For musical notation display Rosegarden-4 uses pixmaps derived from
- the Feta font, part of the Lilypond software (http://lilypond.org/)
- which is Copyright 1997 - 2004 Jan Nieuwenhuizen and Han-Wen Nienhuys.
-
-* Other major contributors include Randall Farmer, Ron Kuris, Hans
- Kieserman, Michael McIntyre, and Pedro Lopez-Cabanillas. See AUTHORS for
- more details, and the individual source files for copyright attributions.
-
-* The Rosegarden splash-screen image is Copyright 2005 Carolyn H. McIntyre,
- used by permission. (It is a photograph of a rose growing in Michael
- McIntyre's real live rose garden.)
-
-Rosegarden-4 is free software; you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation; either version 2 of the License, or (at
-your option) any later version. See the file COPYING included with
-this distribution for more information.
-
Deleted: rosegarden/trunk/SConstruct
===================================================================
--- rosegarden/trunk/SConstruct 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/SConstruct 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,243 +0,0 @@
-#!/usr/bin/python
-## scons script for building rosegarden, adapted from
-## the scons script for building the kde test applications
-## by Thomas Nagy, 2004 (bksys)
-##
-## Guillaume Laurent <glaurent at telegraph-road.org>,
-## Chris Cannam <cannam at all-day-breakfast.com>,
-## Richard Bown <bownie at bownie.com>
-## Stephen Torri <storri at torri.org>
-
-"""
-Extract from bksys doc :
-
-To compile the project, you will then only need to launch
-scons on the top-level directory, the scripts find and
-cache the proper environment automatically :
--> scons
-
-To clean the project
--> scons -c
-
-To install the project
--> scons install
-
-To uninstall the project
--> scons -c install
-
-To compile while being in a subdirectory
--> cd src; scons -u
-
-To (re)configure the project and give particular arguments, use ie :
--> scons configure debug=1
--> scons configure prefix=/tmp/ita debug=full extraincludes=/usr/local/include:/tmp/include prefix=/usr/local
-The variables are saved automatically after the first run
-(look at cache/kde.cache.py, ..)
-
-You can alternate between debug/non-debug mode very easily :
-
-scons configure debug=1; scons; scons configure ;
-"""
-
-# Define the version
-VERSION = "4-1.2.3"
-
-import os
-import glob
-import fnmatch
-import re
-import string
-import sys
-
-env = Environment(TARGS=COMMAND_LINE_TARGETS, ARGS=ARGUMENTS,
- tools = ['default', 'generic', 'kde', 'sound', 'test', 'rosegarden'],
- toolpath=['./', 'scons_admin/'])
-
-#-----------------------------
-# Variables
-#-----------------------------
-
-# Setup the default build directory to c_reldir
-c_builddir = 'RGbuild'
-
-## Exit if configuration requested (scons configure)
-if 'configure' in COMMAND_LINE_TARGETS:
- env.Exit(0)
-#-----------------------------
-# Environment
-#-----------------------------
-env.AppendUnique( ENV = os.environ )
-env.AppendUnique( ENV = {'PATH' : os.environ['PATH'], 'HOME' : os.environ['HOME']} )
-
-## Use this to set rpath - this may cause trouble if folders are moved (chrpath)
-#env.Append( RPATH = [env['QTLIBPATH'], env['KDELIBPATH'], env['KDEMODULE']] )
-
-# Export 'env' so that sconscripts in subdirectories can use it
-Export( "env" )
-
-## The qt library is needed by every sub-program
-env.AppendUnique(LIBS = ['qt-mt'])
-
-## Threading is needed
-env.Append(CCFLAGS = '-DQT_THREAD_SUPPORT')
-
-env.Append(CCFLAGS = '-DVERSION=\\"' + VERSION + '\\"')
-
-##!!! WTF? This is supposed to be defined if NDEBUG is set, which is supposed
-## to happen if debug is not actively requested
-##env.Append(CCFLAGS = '-DNO_TIMING')
-
-#-----------------------------
-# Build
-#-----------------------------
-def givedir(dir):
- return env.join(c_builddir, dir)
-
-SetOption('duplicate', 'soft-copy')
-dirs = env.Split("""
- sound
- sequencer
- gui
- base
-""")
-
-bdirs=[]
-for d in dirs:
- tmpdir = givedir(d)
- env.BuildDir(tmpdir, d)
- bdirs.append(tmpdir)
-env.subdirs(bdirs)
-
-# disable object cache, unless you want it (define the SCONS_CACHE env. var)
-if not os.environ.has_key('SCONS_CACHE'):
- env.CacheDir(None)
-
-#-----------------------------
-# Process the translations
-#-----------------------------
-
-## They are usually located in the po/ directory
-env.KDElang('po/', 'rosegarden')
-
-
-#-----------------------------
-# Installation
-#-----------------------------
-
-if 'install' in COMMAND_LINE_TARGETS:
-
- # .rc files
- env.KDEinstall('KDEDATA','/rosegarden', glob.glob("gui/*.rc"))
-
- # .desktop file
- env.KDEinstall('KDEMENU','/Applications', 'gui/rosegarden.desktop')
-
- # mime files
- mimefiles = """
- gui/x-rosegarden21.desktop
- gui/x-rosegarden.desktop
- gui/x-rosegarden-device.desktop
- gui/x-soundfont.desktop""".split()
-
- env.KDEinstall('KDEMIME','/audio', mimefiles)
-
- # icons
- env.KDEinstallas('KDEICONS','/locolor/16x16/apps/x-rosegarden.xpm', "gui/pixmaps/icons/cc-hi16-rosegarden.xpm")
- env.KDEinstallas('KDEICONS','/hicolor/16x16/apps/x-rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-16x16.png")
-
- env.KDEinstallas('KDEICONS','/hicolor/48x48/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-48x48.png")
- env.KDEinstallas('KDEICONS','/hicolor/64x64/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-64x64.png")
-
- env.KDEinstallas('KDEICONS','/hicolor/128x128/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-128x128.png")
-
- env.KDEinstallas('KDEICONS','/locolor/32x32/apps/rosegarden.xpm', "gui/pixmaps/icons/cc-hi32-rosegarden.xpm")
- env.KDEinstallas('KDEICONS','/hicolor/32x32/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-32x32.png")
-
- env.KDEinstallas('KDEICONS','/hicolor/16x16/mimetypes/x-rosegarden.png', "gui/pixmaps/icons/mm-mime-hi16-rosegarden.png")
- env.KDEinstallas('KDEICONS','/locolor/16x16/mimetypes/x-rosegarden.png', "gui/pixmaps/icons/mm-mime-hi16-rosegarden.png")
-
- env.KDEinstallas('KDEICONS','/hicolor/32x32/mimetypes/x-rosegarden.png', "gui/pixmaps/icons/mm-mime-hi32-rosegarden.png")
- env.KDEinstallas('KDEICONS','/locolor/32x32/mimetypes/x-rosegarden.png', "gui/pixmaps/icons/mm-mime-hi32-rosegarden.png")
-
- # styles
- #for s in glob.glob("gui/styles/*.xml"):
- env.KDEinstall('KDEDATA','/rosegarden/styles', glob.glob("gui/styles/*.xml"))
-
- # fonts
- #for s in glob.glob("gui/fonts/*.pfa"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts', glob.glob("gui/fonts/*.pfa"))
-
- #for s in glob.glob("gui/fonts/mappings/*.xml"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/mappings',glob.glob("gui/fonts/mappings/*.xml"))
-
- #for s in glob.glob("gui/pixmaps/rg21/4/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/rg21/4', glob.glob("gui/pixmaps/rg21/4/*.xpm"))
- #for s in glob.glob("gui/pixmaps/rg21/8/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/rg21/8', glob.glob("gui/pixmaps/rg21/8/*.xpm"))
-
- #for s in glob.glob("gui/pixmaps/feta/4/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/4', glob.glob("gui/pixmaps/feta/4/*.xpm"))
- #for s in glob.glob("gui/pixmaps/feta/6/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/6', glob.glob("gui/pixmaps/feta/6/*.xpm"))
- #for s in glob.glob("gui/pixmaps/feta/8/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/8', glob.glob("gui/pixmaps/feta/8/*.xpm"))
- #for s in glob.glob("gui/pixmaps/feta/10/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/10', glob.glob("gui/pixmaps/feta/10/*.xpm"))
- #for s in glob.glob("gui/pixmaps/feta/12/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/fonts/feta/12', glob.glob("gui/pixmaps/feta/12/*.xpm"))
-
- # pixmaps
- #for s in glob.glob("gui/pixmaps/misc/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/misc', glob.glob("gui/pixmaps/misc/*.xpm"))
-
- #for s in glob.glob("gui/pixmaps/toolbar/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/toolbar', glob.glob("gui/pixmaps/toolbar/*.xpm"))
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/toolbar', glob.glob("gui/pixmaps/toolbar/*.png"))
-
- #for s in glob.glob("gui/pixmaps/transport/*.xpm"):
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/transport', glob.glob("gui/pixmaps/transport/*.xpm"))
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps/transport', glob.glob("gui/pixmaps/transport/*.png"))
-
- env.KDEinstall('KDEDATA','/rosegarden/pixmaps', "gui/pixmaps/splash.png")
-
-
- # examples
- examples="""
- gui/testfiles/glazunov.rg
- gui/testfiles/notation-for-string-orchestra-in-D-minor.rg
- gui/testfiles/ravel-pc-gmaj-adagio.rg
- gui/testfiles/perfect-moment.rg
- gui/testfiles/bwv-1060-brass-band-1-allegro.rg
- gui/testfiles/bogus-surf-jam.rg
- gui/testfiles/the-rose-garden.rg
- gui/testfiles/children.rg
- gui/testfiles/stormy-riders.rg
- gui/testfiles/Djer-Fire.rg""".split()
-
- #for ex in examples:
- env.KDEinstall('KDEDATA','/rosegarden/examples', examples)
-
- # autoload.rg
- env.KDEinstall('KDEDATA', '/rosegarden', "gui/testfiles/autoload.rg")
-
- # tips
- env.KDEinstall('KDEDATA', '/rosegarden', "gui/docs/en/tips")
-
- # library files
- #for l in glob.glob("gui/library/*.rgd"):
- env.KDEinstall('KDEDATA', '/rosegarden/library', glob.glob("gui/library/*.rgd"))
-
- # rosegarden-project-package script
- env.KDEinstall('KDEBIN', '', "gui/rosegarden-project-package" )
-
- # rosegarden-lilypondview script
- env.KDEinstall('KDEBIN', '', "gui/rosegarden-lilypondview" )
-
- # version.txt file
- versionFile = open("version.txt", "w")
- versionFile.write(VERSION + '\n')
- versionFile.close()
- env.KDEinstall('KDEDATA', '/rosegarden', "version.txt")
-
-env.dist('rosegarden', VERSION)
-
Deleted: rosegarden/trunk/TRANSLATORS
===================================================================
--- rosegarden/trunk/TRANSLATORS 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/TRANSLATORS 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,4 +0,0 @@
-Please see the AUTHORS file for a list of translators.
-
-If you'd like to translate Rosegarden into your language, contact us at
-<rosegarden-devel at lists.sourceforge.net>
Property changes on: rosegarden/trunk/debian
___________________________________________________________________
Name: mergeWithUpstream
+ 1
Modified: rosegarden/trunk/debian/changelog
===================================================================
--- rosegarden/trunk/debian/changelog 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/debian/changelog 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,5 +1,6 @@
-rosegarden (1:1.2.3-1) unstable; urgency=low
+rosegarden (1:1.2.3-1) UNRELEASED; urgency=low
+ [Mike O'Connor]
* New Maintainer (Closes: #352541)
* New upstream version
* No longer building a verbose debug version (Closes: #311087)
@@ -7,9 +8,12 @@
* Split arch-indep files into a rosegarden4-data pacakge (Closes: #233437)
* The upstream menu icon is now included (Closes: #299390)
* Moved jackd from Depends: to Recommends: (Closes: #219286)
-
- -- Mike O'Connor <stew at vireo.org> Fri, 17 Feb 2006 11:01:48 -0500
+ [Free Ekanayaka]
+ * Using dpatch to manage changes to upstream code
+
+ -- Free Ekanayaka <freee at debian.org> Wed, 7 Jun 2006 12:16:42 +0200
+
rosegarden4 (1.0-1.2) unstable; urgency=low
* Non-maintainer upload.
Modified: rosegarden/trunk/debian/control
===================================================================
--- rosegarden/trunk/debian/control 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/debian/control 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,8 +1,9 @@
Source: rosegarden
Section: sound
Priority: optional
-Maintainer: Mike O'Connor <stew at vireo.org>
-Build-Depends: debhelper (>> 4.0.0), scons, kdelibs4-dev, libasound2-dev (>= 1.0.0), libjack-dev, ladspa-sdk, liblrdf0-dev, liblircclient-dev, dssi-dev (>= 0.4 ), liblo0-dev (>= 0.7), libxft-dev
+Maintainer: Debian Multimedia Team <debian-multimedia at lists.debian.org>
+Uploaders: Mike O'Connor <stew at vireo.org>, Free Ekanayaka <freee at debian.org>
+Build-Depends: debhelper (>> 4.0.0), scons, kdelibs4-dev, libasound2-dev (>= 1.0.0), libjack-dev, ladspa-sdk, liblrdf0-dev, liblircclient-dev, dssi-dev (>= 0.4 ), liblo0-dev (>= 0.7), libxft-dev, dpatch
Standards-Version: 3.6.2
Package: rosegarden
Added: rosegarden/trunk/debian/patches/00list
===================================================================
--- rosegarden/trunk/debian/patches/00list 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/debian/patches/00list 2006-06-07 10:25:09 UTC (rev 796)
@@ -0,0 +1,2 @@
+10_install-list
+20_env
Added: rosegarden/trunk/debian/patches/10_install-list.dpatch
===================================================================
--- rosegarden/trunk/debian/patches/10_install-list.dpatch 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/debian/patches/10_install-list.dpatch 2006-06-07 10:25:09 UTC (rev 796)
@@ -0,0 +1,19 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 10_install-list.dpatch by Free Ekanayaka <free at 64studio.com>
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: No description.
+
+ at DPATCH@
+diff -urNad rosegarden-1.2.3.orig~/scons_admin/kde.py rosegarden-1.2.3.orig/scons_admin/kde.py
+--- rosegarden-1.2.3.orig~/scons_admin/kde.py 2005-08-26 22:37:44.000000000 +0200
++++ rosegarden-1.2.3.orig/scons_admin/kde.py 2006-06-07 11:12:24.000000000 +0200
+@@ -533,7 +533,7 @@
+ def KDEinstallas(lenv, restype, destfile, file):
+ if not env['_INSTALL']: return
+ dir = getInstDirForResType(lenv, restype)
+- install_list = lenv.InstallAs(lenv.join(dir, destfile), file)
++ install_list = lenv.bksys_install(dir, [file], destfile)
+ env.Alias('install', install_list)
+ return install_list
+
Property changes on: rosegarden/trunk/debian/patches/10_install-list.dpatch
___________________________________________________________________
Name: svn:executable
+ *
Added: rosegarden/trunk/debian/patches/20_env.dpatch
===================================================================
--- rosegarden/trunk/debian/patches/20_env.dpatch 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/debian/patches/20_env.dpatch 2006-06-07 10:25:09 UTC (rev 796)
@@ -0,0 +1,28 @@
+#! /bin/sh /usr/share/dpatch/dpatch-run
+## 20_env.dpatch by Free Ekanayaka <free at 64studio.com>
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: No description.
+
+ at DPATCH@
+diff -urNad rosegarden-1.2.3.orig~/SConstruct rosegarden-1.2.3.orig/SConstruct
+--- rosegarden-1.2.3.orig~/SConstruct 2006-02-14 08:55:21.000000000 +0100
++++ rosegarden-1.2.3.orig/SConstruct 2006-06-07 11:13:54.000000000 +0200
+@@ -70,7 +70,7 @@
+ env.AppendUnique( ENV = {'PATH' : os.environ['PATH'], 'HOME' : os.environ['HOME']} )
+
+ ## Use this to set rpath - this may cause trouble if folders are moved (chrpath)
+-env.Append( RPATH = [env['QTLIBPATH'], env['KDELIBPATH'], env['KDEMODULE']] )
++#env.Append( RPATH = [env['QTLIBPATH'], env['KDELIBPATH'], env['KDEMODULE']] )
+
+ # Export 'env' so that sconscripts in subdirectories can use it
+ Export( "env" )
+@@ -143,7 +143,7 @@
+
+ # icons
+ env.KDEinstallas('KDEICONS','/locolor/16x16/apps/x-rosegarden.xpm', "gui/pixmaps/icons/cc-hi16-rosegarden.xpm")
+- env.KDEinstallas('KDEICONS','/hicolor/16x16/apps/x-rosegarden.xpm', "gui/pixmaps/icons/rg-rwb-rose3-16x16.png")
++ env.KDEinstallas('KDEICONS','/hicolor/16x16/apps/x-rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-16x16.png")
+
+ env.KDEinstallas('KDEICONS','/hicolor/48x48/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-48x48.png")
+ env.KDEinstallas('KDEICONS','/hicolor/64x64/apps/rosegarden.png', "gui/pixmaps/icons/rg-rwb-rose3-64x64.png")
Property changes on: rosegarden/trunk/debian/patches/20_env.dpatch
___________________________________________________________________
Name: svn:executable
+ *
Modified: rosegarden/trunk/debian/rules
===================================================================
--- rosegarden/trunk/debian/rules 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/debian/rules 2006-06-07 10:25:09 UTC (rev 796)
@@ -5,6 +5,8 @@
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
+include /usr/share/dpatch/dpatch.make
+
DEB_BUILD_ARCH := $(shell dpkg --print-installation-architecture)
ARCH=$(DEB_BUILD_ARCH)
@@ -46,14 +48,14 @@
build: build-stamp
-build-stamp: configure-stamp
+build-stamp: configure-stamp patch-stamp
dh_testdir
scons CACHEDIR=.scons-cache
touch build-stamp
-clean:
+clean: unpatch
dh_testdir
dh_testroot
scons -c CACHEDIR=.scons-cache
Deleted: rosegarden/trunk/rosegarden.lsm
===================================================================
--- rosegarden/trunk/rosegarden.lsm 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/rosegarden.lsm 2006-06-07 10:25:09 UTC (rev 796)
@@ -1,14 +0,0 @@
-Begin3
-Title: Rosegarden-4
-Version: 1.2.3
-Entered-date:
-Description: MIDI and audio sequencer and musical notation editor
-Keywords: KDE Qt JACK ALSA
-Author: Guillaume Laurent <glaurent at telegraph-road.org>, Chris Cannam <cannam at all-day-breakfast.com>, Richard Bown <bownie at bownie.com>
-Maintained-by: Guillaume Laurent <glaurent at telegraph-road.org>, Chris Cannam <cannam at all-day-breakfast.com>, Richard Bown <bownie at bownie.com>
-Home-page: http://www.rosegardenmusic.com/
-Alternate-site:
-Primary-site:
-Platform: Linux
-Copying-policy: GPL
-End
Deleted: rosegarden/trunk/version.txt
===================================================================
--- rosegarden/trunk/version.txt 2006-06-06 14:48:58 UTC (rev 795)
+++ rosegarden/trunk/version.txt 2006-06-07 10:25:09 UTC (rev 796)
@@ -1 +0,0 @@
-4-1.2.3
More information about the Demudi-commits
mailing list