https://gramps-project.org/wiki/api.php?action=feedcontributions&user=Graibeard&feedformat=atomGramps - User contributions [en]2024-03-29T07:18:17ZUser contributionsMediaWiki 1.31.3https://gramps-project.org/wiki/index.php?title=Addon:CombinedView&diff=85902Addon:CombinedView2021-07-03T03:09:35Z<p>Graibeard: make that 2 typos</p>
<hr />
<div>{{Third-party plugin}}<br />
<!-- [[File:combindedview-example-51.png|450px|thumb|right|Combined View - addon - In action showing ]] --><br />
The Combined View is a {{man label|Relationships}} category view addon that shows relationships and events for a person. It is similar to the built-in [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships View]] that gives an overview of how records relate to each other within the context of a specific person ... but on steroids.<br />
<br />
This view is intentionally 'read only' with no editing controls.<br />
<br />
{{stub}}<br />
<br />
== Usage ==<br />
{{-}}<br />
=== Relationships tab ===<br />
[[File:CombinedView-Relationships-tab-example-51.png|right|450px|thumb]]<br />
Relationships (Default) tab<br />
{{-}}<br />
=== Events tab ===<br />
[[File:CombinedView-Events-tab-example-51.png|right|450px|thumb]]<br />
{{-}}<br />
=== Album tab ===<br />
[[File:CombinedView-Album-tab-example-51.png|right|450px|thumb]]<br />
{{-}}<br />
=== Timeline tab ===<br />
[[File:CombinedView-Timeline-tab-example-51.png|right|450px|thumb]]<br />
{{-}}<br />
=== Associations tab ===<br />
[[File:CombinedView-Associations-tab-example-51.png|right|450px|thumb]]<br />
{{-}}<br />
=== Configure Options ===<br />
<br />
==== Content tab ====<br />
[[File:CombinedView-ConfigureOptions-Content-defaults-51.png|right|450px|thumb]]<br />
{{-}}<br />
==== Layout tab ====<br />
[[File:CombinedView-ConfigureOptions-Layout-defaults-51.png|right|450px|thumb]]<br />
{{-}}<br />
<br />
== See also ==<br />
* [https://sourceforge.net/p/gramps/mailman/message/36982096/ New experimental combined view] 2020-04-15 - initial announcement by Nick Hall <br />
<br />
== Issues ==<br />
See issues tagged [https://gramps-project.org/bugs/tag_view_page.php?tag_id=337 CombinedView]<br />
<br />
[[Category:Plugins]]<br />
[[Category:Developers/General]]<br />
[[Category:Views]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Addon:CombinedView&diff=85901Addon:CombinedView2021-07-03T03:07:43Z<p>Graibeard: grammar ; typo</p>
<hr />
<div>{{Third-party plugin}}<br />
<!-- [[File:combindedview-example-51.png|450px|thumb|right|Combined View - addon - In action showing ]] --><br />
The Combinded View is a {{man label|Relationships}} category view addon that shows relationships and events for a person. It is similar to the built-in [[Gramps_{{man version}}_Wiki_Manual_-_Categories#Relationships_Category|Relationships View]] that gives an overview of how records relate to each other within the context of a specific person ... but on steroids.<br />
<br />
This view is intentionally 'read only' with no editing controls.<br />
<br />
{{stub}}<br />
<br />
== Usage ==<br />
{{-}}<br />
=== Relationships tab ===<br />
[[File:CombinedView-Relationships-tab-example-51.png|right|450px|thumb]]<br />
Relationships (Default) tab<br />
{{-}}<br />
=== Events tab ===<br />
[[File:CombinedView-Events-tab-example-51.png|right|450px|thumb]]<br />
{{-}}<br />
=== Album tab ===<br />
[[File:CombinedView-Album-tab-example-51.png|right|450px|thumb]]<br />
{{-}}<br />
=== Timeline tab ===<br />
[[File:CombinedView-Timeline-tab-example-51.png|right|450px|thumb]]<br />
{{-}}<br />
=== Associations tab ===<br />
[[File:CombinedView-Associations-tab-example-51.png|right|450px|thumb]]<br />
{{-}}<br />
=== Configure Options ===<br />
<br />
==== Content tab ====<br />
[[File:CombinedView-ConfigureOptions-Content-defaults-51.png|right|450px|thumb]]<br />
{{-}}<br />
==== Layout tab ====<br />
[[File:CombinedView-ConfigureOptions-Layout-defaults-51.png|right|450px|thumb]]<br />
{{-}}<br />
<br />
== See also ==<br />
* [https://sourceforge.net/p/gramps/mailman/message/36982096/ New experimental combined view] 2020-04-15 - initial announcement by Nick Hall <br />
<br />
== Issues ==<br />
See issues tagged [https://gramps-project.org/bugs/tag_view_page.php?tag_id=337 CombinedView]<br />
<br />
[[Category:Plugins]]<br />
[[Category:Developers/General]]<br />
[[Category:Views]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_User_Directory&diff=76183Gramps 5.1 Wiki Manual - User Directory2020-03-19T02:13:44Z<p>Graibeard: /* POSIX - style systems */ oops: Fix for naming consistency</p>
<hr />
<div>{{man index|Gramps_5.1_Wiki_Manual_-_Command_Line#Environment_variables|Gramps 5.1 Wiki Manual - Error and Warning Reference|5.1}} <br />
{{languages|Gramps_5.1_Wiki_Manual_-_User_Directory}}<br />
{{#vardefine:chapter|D}}<br />
{{#vardefine:figure|0}}<br />
This appendix provides the reference to the '''Gramps user directory''' available on various operating systems.<br />
<br />
{{man note|Note|The location of your '''Gramps user directory''' depends on the operating system you are using and how you have set up your computer. <br />In the table below '''''<code><~username></code>''''' should be replaced by the name you use to log in to your computer.}}<br />
<br />
__TOC__<br />
== [[Gramps_Glossary#posix|POSIX]] - style systems ==<br />
The default user directory location for Gramps in a [https://wikipedia.org/wiki/Posix POSIX]-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment] is:<br />
<br />
/HOME/'''''<username>'''''/.gramps<br />
which can also be entered as<br />
'''''<~username>'''''/.gramps<br />
<br />
This is true for [https://wikipedia.org/wiki/Bsd BSD], [https://wikipedia.org/wiki/Linux Linux], [https://wikipedia.org/wiki/Solaris_(operating_system) Solaris], [https://wikipedia.org/wiki/Unix Unix] and [https://wikipedia.org/wiki/Mac_OS_X Mac OS-X] when using [[Build_from_source#Mac_OS_X|Mac OS X Build from source]].<br />
<br />
Alternately, you can leverage the '''$HOME''' [http://www.linfo.org/home_directory.html Home directory equivalent] to avoid dealing the complications of active user names. Although Gramps will not recognize directory equivalents for paths internally, you can use them within Linux to find Gramps user files. The '''Gramps user directory''' path above is simplified to either:<br />
<br />
$HOME/.gramps<br />
or<br />
~/.gramps<br />
<br />
Or if using MS Windows the following syntax is used<br />
<br />
$HOME\.gramps<br />
or<br />
~\.gramps<br />
<br />
=== Mac OS X ===<br />
[[File:macos_200x200.png|right|128px|link=Download#Mac_OS_X]]<br />
On Apple Macs running OS X, filenames starting with "." do not show up in Finder. To make access to the Gramps user directory easy, open a terminal window with Finder-Applications-Utilities-Terminal and type there<br />
ln -s .gramps gramps_user_directory<br />
which will allow Finder to show the contents. Or simply click on Go -> 'Go to Folder...' in the Finder, and type<br />
~/.gramps<br />
in the Go to Folder dialog box.<br />
<br />
The default location for the [[Mac OS X:Application package]] is<br />
/Users/'''''<~username>'''''/Library/Application Support/gramps<br />
<br />
== MS Windows ==<br />
[[File:windows_180x160.png|right|128px|link=Download#MS_Windows]]On Microsoft Windows, filenames and folder for programs and userdata are [https://wikipedia.org/wiki/Hidden_file_and_hidden_directory hidden] in the ''File Explorer''. To make access to the Gramps user directory easy follow the following advice from Microsoft:<br />
* [https://support.microsoft.com/en-ca/help/14201/windows-show-hidden-files Show hidden files - Windows Help]<br />
<br />
The default location for an installation on a Windows 7 (and newer) system is <br />
C:\Program Files\GrampsAIO64-5.X.X<br />
or<br />
C:\Program Files (x86)\GrampsAIO32-5.X.X<br />
<br />
<br />
The default location for any Gramps user data on a Windows 7 (and newer) system is <br />
C:\Users\'''''<~username>'''''\AppData\Roaming\gramps<br />
<br />
Alternately, you can leverage the '''%AppData%''' [https://wikipedia.org/wiki/Environment_variable#APPDATA environment variable] to avoid dealing the complications of active user names. Although Gramps will not recognize Environment Variables for paths internally, you can use them within Windows to find Gramps user files. The '''Gramps user directory''' path above is simplified to:<br />
%AppData%\gramps<br />
{{-}}<br />
{{man index|Gramps_5.1_Wiki_Manual_-_Command_Line#Environment_variables|Gramps 5.1 Wiki Manual - Error and Warning Reference|5.1}} <br />
{{languages|Gramps_5.1_Wiki_Manual_-_User_Directory}}<br />
{{grampsmanualcopyright}}<br />
[[Category:Documentation|U]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_User_Directory&diff=76182Gramps 5.1 Wiki Manual - User Directory2020-03-19T02:10:47Z<p>Graibeard: /* POSIX - style systems */ Slipped in corrected "/" for Linux usage. Assuming the original entry "\" was for POSIX windows so note added</p>
<hr />
<div>{{man index|Gramps_5.1_Wiki_Manual_-_Command_Line#Environment_variables|Gramps 5.1 Wiki Manual - Error and Warning Reference|5.1}} <br />
{{languages|Gramps_5.1_Wiki_Manual_-_User_Directory}}<br />
{{#vardefine:chapter|D}}<br />
{{#vardefine:figure|0}}<br />
This appendix provides the reference to the '''Gramps user directory''' available on various operating systems.<br />
<br />
{{man note|Note|The location of your '''Gramps user directory''' depends on the operating system you are using and how you have set up your computer. <br />In the table below '''''<code><~username></code>''''' should be replaced by the name you use to log in to your computer.}}<br />
<br />
__TOC__<br />
== [[Gramps_Glossary#posix|POSIX]] - style systems ==<br />
The default user directory location for Gramps in a [https://wikipedia.org/wiki/Posix POSIX]-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment] is:<br />
<br />
/HOME/'''''<username>'''''/.gramps<br />
which can also be entered as<br />
'''''<~username>'''''/.gramps<br />
<br />
This is true for [https://wikipedia.org/wiki/Bsd BSD], [https://wikipedia.org/wiki/Linux Linux], [https://wikipedia.org/wiki/Solaris_(operating_system) Solaris], [https://wikipedia.org/wiki/Unix Unix] and [https://wikipedia.org/wiki/Mac_OS_X Mac OS-X] when using [[Build_from_source#Mac_OS_X|Mac OS X Build from source]].<br />
<br />
Alternately, you can leverage the '''$HOME''' [http://www.linfo.org/home_directory.html Home directory equivalent] to avoid dealing the complications of active user names. Although Gramps will not recognize directory equivalents for paths internally, you can use them within Linux to find Gramps user files. The '''Gramps user directory''' path above is simplified to either:<br />
<br />
$HOME/.gramps<br />
or<br />
~/.gramps<br />
<br />
Or if using Windows the following syntax is used<br />
<br />
$HOME\.gramps<br />
or<br />
~\.gramps<br />
<br />
=== Mac OS X ===<br />
[[File:macos_200x200.png|right|128px|link=Download#Mac_OS_X]]<br />
On Apple Macs running OS X, filenames starting with "." do not show up in Finder. To make access to the Gramps user directory easy, open a terminal window with Finder-Applications-Utilities-Terminal and type there<br />
ln -s .gramps gramps_user_directory<br />
which will allow Finder to show the contents. Or simply click on Go -> 'Go to Folder...' in the Finder, and type<br />
~/.gramps<br />
in the Go to Folder dialog box.<br />
<br />
The default location for the [[Mac OS X:Application package]] is<br />
/Users/'''''<~username>'''''/Library/Application Support/gramps<br />
<br />
== MS Windows ==<br />
[[File:windows_180x160.png|right|128px|link=Download#MS_Windows]]On Microsoft Windows, filenames and folder for programs and userdata are [https://wikipedia.org/wiki/Hidden_file_and_hidden_directory hidden] in the ''File Explorer''. To make access to the Gramps user directory easy follow the following advice from Microsoft:<br />
* [https://support.microsoft.com/en-ca/help/14201/windows-show-hidden-files Show hidden files - Windows Help]<br />
<br />
The default location for an installation on a Windows 7 (and newer) system is <br />
C:\Program Files\GrampsAIO64-5.X.X<br />
or<br />
C:\Program Files (x86)\GrampsAIO32-5.X.X<br />
<br />
<br />
The default location for any Gramps user data on a Windows 7 (and newer) system is <br />
C:\Users\'''''<~username>'''''\AppData\Roaming\gramps<br />
<br />
Alternately, you can leverage the '''%AppData%''' [https://wikipedia.org/wiki/Environment_variable#APPDATA environment variable] to avoid dealing the complications of active user names. Although Gramps will not recognize Environment Variables for paths internally, you can use them within Windows to find Gramps user files. The '''Gramps user directory''' path above is simplified to:<br />
%AppData%\gramps<br />
{{-}}<br />
{{man index|Gramps_5.1_Wiki_Manual_-_Command_Line#Environment_variables|Gramps 5.1 Wiki Manual - Error and Warning Reference|5.1}} <br />
{{languages|Gramps_5.1_Wiki_Manual_-_User_Directory}}<br />
{{grampsmanualcopyright}}<br />
[[Category:Documentation|U]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_5.1_Wiki_Manual_-_User_Directory&diff=76181Gramps 5.1 Wiki Manual - User Directory2020-03-19T02:05:25Z<p>Graibeard: /* POSIX - style systems */ lowercase for actual directory (upper for variable), redundant ~ removed. Both styles confirmed using Linux CLI</p>
<hr />
<div>{{man index|Gramps_5.1_Wiki_Manual_-_Command_Line#Environment_variables|Gramps 5.1 Wiki Manual - Error and Warning Reference|5.1}} <br />
{{languages|Gramps_5.1_Wiki_Manual_-_User_Directory}}<br />
{{#vardefine:chapter|D}}<br />
{{#vardefine:figure|0}}<br />
This appendix provides the reference to the '''Gramps user directory''' available on various operating systems.<br />
<br />
{{man note|Note|The location of your '''Gramps user directory''' depends on the operating system you are using and how you have set up your computer. <br />In the table below '''''<code><~username></code>''''' should be replaced by the name you use to log in to your computer.}}<br />
<br />
__TOC__<br />
== [[Gramps_Glossary#posix|POSIX]] - style systems ==<br />
The default user directory location for Gramps in a [https://wikipedia.org/wiki/Posix POSIX]-style [https://wikipedia.org/wiki/Filesystem_Hierarchy_Standard environment] is:<br />
<br />
/HOME/'''''<username>'''''/.gramps<br />
which can also be entered as<br />
'''''<~username>'''''/.gramps<br />
<br />
This is true for [https://wikipedia.org/wiki/Bsd BSD], [https://wikipedia.org/wiki/Linux Linux], [https://wikipedia.org/wiki/Solaris_(operating_system) Solaris], [https://wikipedia.org/wiki/Unix Unix] and [https://wikipedia.org/wiki/Mac_OS_X Mac OS-X] when using [[Build_from_source#Mac_OS_X|Mac OS X Build from source]].<br />
<br />
Alternately, you can leverage the '''$HOME''' [http://www.linfo.org/home_directory.html Home directory equivalent] to avoid dealing the complications of active user names. Although Gramps will not recognize directory equivalents for paths internally, you can use them within Linux to find Gramps user files. The '''Gramps user directory''' path above is simplified to either:<br />
$HOME\.gramps<br />
or<br />
~\.gramps<br />
<br />
=== Mac OS X ===<br />
[[File:macos_200x200.png|right|128px|link=Download#Mac_OS_X]]<br />
On Apple Macs running OS X, filenames starting with "." do not show up in Finder. To make access to the Gramps user directory easy, open a terminal window with Finder-Applications-Utilities-Terminal and type there<br />
ln -s .gramps gramps_user_directory<br />
which will allow Finder to show the contents. Or simply click on Go -> 'Go to Folder...' in the Finder, and type<br />
~/.gramps<br />
in the Go to Folder dialog box.<br />
<br />
The default location for the [[Mac OS X:Application package]] is<br />
/Users/'''''<~username>'''''/Library/Application Support/gramps<br />
<br />
== MS Windows ==<br />
[[File:windows_180x160.png|right|128px|link=Download#MS_Windows]]On Microsoft Windows, filenames and folder for programs and userdata are [https://wikipedia.org/wiki/Hidden_file_and_hidden_directory hidden] in the ''File Explorer''. To make access to the Gramps user directory easy follow the following advice from Microsoft:<br />
* [https://support.microsoft.com/en-ca/help/14201/windows-show-hidden-files Show hidden files - Windows Help]<br />
<br />
The default location for an installation on a Windows 7 (and newer) system is <br />
C:\Program Files\GrampsAIO64-5.X.X<br />
or<br />
C:\Program Files (x86)\GrampsAIO32-5.X.X<br />
<br />
<br />
The default location for any Gramps user data on a Windows 7 (and newer) system is <br />
C:\Users\'''''<~username>'''''\AppData\Roaming\gramps<br />
<br />
Alternately, you can leverage the '''%AppData%''' [https://wikipedia.org/wiki/Environment_variable#APPDATA environment variable] to avoid dealing the complications of active user names. Although Gramps will not recognize Environment Variables for paths internally, you can use them within Windows to find Gramps user files. The '''Gramps user directory''' path above is simplified to:<br />
%AppData%\gramps<br />
{{-}}<br />
{{man index|Gramps_5.1_Wiki_Manual_-_Command_Line#Environment_variables|Gramps 5.1 Wiki Manual - Error and Warning Reference|5.1}} <br />
{{languages|Gramps_5.1_Wiki_Manual_-_User_Directory}}<br />
{{grampsmanualcopyright}}<br />
[[Category:Documentation|U]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=A_Translators_Guide_to_Git&diff=70960A Translators Guide to Git2019-01-06T01:59:25Z<p>Graibeard: /* Updating a translation */ prefer? like? -- 'like' used</p>
<hr />
<div>= Configuration =<br />
<br />
Git includes your name and email address in commits. To configure them, use the following commands: <br />
git config --global user.name "John Smith"<br />
git config --global user.email john@example.com<br />
<br />
Git will automatically convert line endings for you. Use the following settings:<br />
git config --global core.autocrlf true # Windows<br />
git config --global core.autocrlf input # Linux/Mac<br />
<br />
The following configuration option simplifies pushing a branch back to the server:<br />
git config --global push.default upstream<br />
<br />
= Obtain a copy of the repository =<br />
<br />
Clone the repository:<br />
git clone git@github.com:gramps-project/gramps.git Gramps<br />
<br />
Change directory:<br />
cd Gramps<br />
<br />
= Create a maintenance branch =<br />
<br />
To create a local branch which tracks a branch on the server, use:<br />
<br />
git checkout -b gramps50 origin/maintenance/gramps50<br />
<br />
= Updating a translation =<br />
<br />
There are two main workflows. The basic workflow is simpler, but is only available to developers that have write access to the repository. Otherwise translators should create a pull request. This may also be preferred by translators who are new to Git and would like their contribution checked before it is pushed to the repository.<br />
<br />
== Basic workflow ==<br />
<br />
Checkout the maintenance branch:<br />
git checkout gramps50<br />
<br />
Get the latest changes:<br />
git pull --rebase<br />
<br />
Now edit the po file.<br />
<br />
Check status and differences:<br />
git status<br />
git diff<br />
<br />
Stage the file for commit:<br />
git add po/xx.po<br />
<br />
Commit the change:<br />
git commit -m 'Update xx translation'<br />
<br />
Get the latest changes again:<br />
git pull --rebase<br />
<br />
Always use the '--rebase' option.<br />
<br />
Check the log:<br />
git log<br />
<br />
Check using a graphical tool:<br />
gitk<br />
<br />
Look for anything unusual such as merge commits.<br />
<br />
When you are completely happy, push the changes to the server. If in doubt, don't.<br />
<br />
== Creating a pull request ==<br />
<br />
Fork the Gramps repository in GitHub. To do this, go to the gramps repository page,<br />
<br />
https://github.com/gramps-project/gramps<br />
<br />
then login, and click on the "Fork" button.<br />
<br />
Create a remote to access you fork:<br />
<br />
git remote add myfork git@github.com:''<username>''/gramps.git<br />
<br />
where ''<username>'' is you GitHub username.<br />
<br />
Create a branch to work in:<br />
<br />
git checkout -b xx gramps50<br />
<br />
Now edit the po file.<br />
<br />
Commit your changes:<br />
git add po/xx.po<br />
git commit -m 'Update xx translation'<br />
<br />
You can update the ''gramps50'' branch at any time.<br />
<br />
git checkout gramps50<br />
git pull<br />
<br />
You rebase your working branch on the ''gramps50'' branch at any time.<br />
<br />
git checkout xx<br />
git rebase gramps50<br />
<br />
When you are ready to make a pull request, push your translation to your fork:<br />
git push myfork xx<br />
<br />
Now create a pull request within GitHub.<br />
<br />
If you have recently pushed a branch to your fork, then GitHub will highlight this when you visit the repository page, and give you an option to create a pull request. Otherwise click on the "New pull request" button.<br />
<br />
Make sure that you select "gramps50" as the base branch.<br />
<br />
==See also==<br />
* [[Portal:Translators]]<br />
* [[Translating Gramps]]<br />
<br />
[[Category:Translators/Categories]]<br />
[[Category:Community/General]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Example.gramps&diff=70421Example.gramps2018-10-14T02:00:03Z<p>Graibeard: example.gramps.gz can be renamed rather than extracted.</p>
<hr />
<div>Your installation of Gramps should include an example family tree database. This is used to provide a known stable environment for testing, for working through tutorials, and for experimenting.<br />
<br />
If you think you have an issue/bug in your ''Family Tree''/database, try the same operation with the example family tree. If the problem happens there as well, then it is probably not due to a [[Recover corrupted family tree|corruption in your data]].<br />
<br />
==Load <code>example.gramps</code>==<br />
Follow these steps to load the example family tree:<br />
# Find <code>example.gramps.gz</code> or <code>example.gramps</code> on your system. For example:<br />
#* on Linux <code>/usr/share/doc/gramps/example/gramps/</code>. If the file is named <code>example.gramps.gz</code>, rename it to <code>example.gramps</code> and gramps will recognize it. You can copy this file to a temporary location or import it directly from this directory.<br />
#* on MS-Windows AIO <code>C:\Program Files\GrampsAIO64-X.X.X\share\doc\gramps\example\gramps</code> (On MS-Windows ensure you can see hidden files; see [[Gramps_5.0_Wiki_Manual_-_User_Directory#MS_Windows|User Directory:MS Windows]])<br />
#* The example database is not included in the MacOS AIO.<br />
# Start Gramps<br />
# To create a new family tree {{man menu|Family Trees > Manage Family Trees...}} select the {{man button|New}} button. Give it some name, such as ''example''<br />
# Open this new family tree. It will be empty.<br />
# In Gramps, use {{man menu|Family Trees > Import...}} to [[Gramps_5.0_Wiki_Manual_-_Manage_Family_Trees#Importing_data|import]] <code>example.gramps</code>.<br />
#;Import Statistics of the example.gramps family tree <br />
{| class="wikitable"<br />
|<br />
Number of new objects imported:<br />
* People: 2157<br />
* Families: 762<br />
* [[Sources|{{man label|Sources}}]]: 4<br />
* [[Events_in_Gramps|{{man label|Events}}]]: 3432<br />
* Media Objects: 7<br />
* [[Places_in_Gramps|{{man label|Places}}]]: 1294<br />
* [[Repositories_in_Gramps|{{man label|Repositories}}]]: 3<br />
* Notes: 19<br />
* [[Tags_in_Gramps|{{man label|Tags}}]]: 2<br />
* [[Citations#Why_Cite|{{man label|Citations}}]]: 2854<br />
<br />
Media objects with relative paths have been<br />
imported. These paths are considered relative to<br />
the media directory you can set in the preferences,<br />
or, if not set, relative to the user's directory.<br />
|[[File:GEDCOM-ImportStatistics-dialog-50.png|right|200px|thumb|Fig. {{#var:chapter}}.{{#vardefineecho:figure|{{#expr:{{#var:figure}}+1}}}} Import Statistics - dialog]]<br />
|}<br />
==Connecting to the example Media Objects==<br />
There are seven example Media Objects (JPEG and PNG images) provided but the relative media path starting point (the Base Path) hasn't been defined in the Preferences. So these images won't be displayed until the media path has been re-defined. The media path can be reset now or if starting to experiment with images. <br />
# In {{man menu|Edit > Preferences}}, change the {{man label|Base path for relative media paths:}} in the [[Gramps_5.0_Wiki_Manual_-_Settings#General|{{man label|General}}]] tab. This could be in a new directory, to keep it separate to your own family tree media. (eg On Linux <code>~/gramps/example/</code>)<br />
# Copy the media files from the example directory (that you found in step 1, above) to this media path directory. <br />
{{man note|The example.gramps family tree data file| Alternately, a replacement Gramps ''[https://raw.githubusercontent.com/gramps-project/gramps/maintenance/gramps50/example/gramps/example.gramps example.gramps]'' [[XML|{{man label|XML}}]] family tree database file (without the Media Objects) can be downloaded from the GitHub file store.}}<br />
==See also==<br />
* [[How to make a backup]]<br />
* [[Recover corrupted family tree]]<br />
* [[Data.gramps]]<br />
<br />
[[Category:Documentation]]<br />
[[Category:Gramps Examples]]<br />
[[Category:Genealogy]]<br />
[[Category:Developers/General]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=How_to_create_a_good_bug_report&diff=70405How to create a good bug report2018-10-12T11:23:33Z<p>Graibeard: Link to example database page. remove stale directory link. Tweak text.</p>
<hr />
<div>Any complex piece of software will contain bugs and Gramps is no exception. Testing before a new release is made allows us to identify and fix all of the obvious bugs, however more obscure ones will inevitably make it into the final release. Reporting bugs is one of the best things that Gramps users can do to help the project improve the software, but the developers only have a chance to fix bugs if they can reproduce the bugs themselves. This can be difficult and time consuming for more obscure ones. It's important to realise that a good bug report which easily allows a developer to reproduce the bug is more likely to get the developer's attention and the bug fixed. This page describes how to make a good bug report.<br />
<br />
Such a report can then be submitted on the bug tracker: [http://bugs.gramps-project.org/ http://bugs.gramps-project.org/]<br />
<br />
==Creating a test database==<br />
The Gramps developers do not have access to a user's computer or database and for data privacy reasons a user is normally unwilling to send a copy of their database to a developer. Bugs that cause data corruption usually mean that the symptoms of the bug are only visible in the user's database.<br />
<br />
To work around this problem, you can try and reproduce the bug yourself using a test database. Each installation of Gramps comes with a small set of example data that you can use to create this test database.<br />
<br />
If you can reproduce the bug in the test database and you record the steps taken to producing the bug then there is a good chance that a developer can do the same. <br />
<br />
Here is how to create your test database.<br />
<br />
# Open the Family Tree Manager and create a new database.<br />
# [[Example.gramps|Import the example data set]] into this empty, new database. You will find the example data in a file called example/gramps/data.gramps. The actual location of this directory will depend on where you have installed Gramps on your system, the previous link contains those details.<br />
<br />
The example data set contains people, families and events that you can use to try and reproduce the problem.<br />
<br />
==Reproducing the bug==<br />
Bugs come in many different shapes and sizes. Some bugs just cause unexpected behaviour. Others are more serious and can cause Gramps to crash. The worst bugs are those that cause some data corruption in the database. Identifying the source of the bug is the hard part because the problem you see might just be a symptom of the bug and not the actual bug itself. These types of bugs often don't show any signs when the corruption is occurring. You only notice the symptoms of the bug when another part of Gramps tries to use the corrupted data. Here are some tips to help you reproduce the bug. If you succeed in getting the test database to cause the same symptoms then record the sequence of steps it took you to reproduce the problem.<br />
<br />
* The first thing to try in your test database is to simply do whatever you did in your own database that caused the bug symptoms to occur. For example, if you crashed your own database running a report on a person then pick a person in the test database and run the same report there.<br />
<br />
* Try performing some of the typical editing actions you perform on your own data and then run whatever action causes the symptoms to occur. Try doing things like adding and removing children from families. Try adding and removing events, sources and notes. Maybe you have performed one of these actions in your own database and there is a bug that has caused some data corruption that has gone unnoticed.<br />
<br />
* The next thing to look at is the types of data you have been putting in your own database. Perhaps the problem is related to something unusual that you have added that Gramps cannot handle. With this type of problem you might find in your own database that Gramps shows the bug symptoms with one person, family, event (or whatever) but not another. Try and reproduce the same types of data in your test database and see if you get the same symptoms.<br />
<br />
* Don't be afraid to delete and re-create your test database to keep it fresh. What you should be aiming for is to reproduce the bug with the minimum number of changes to the pristine example data set.<br />
<br />
==Recording the steps that reproduce the bug==<br />
When you have reached the point where you can consistently re-create your problem using your test database you should then open a bug report and document the steps you took to produce the problem. Make sure that you record your instructions in explicit detail so that a developer can follow your exact steps.<br />
<br />
State which people, families etc that you are using by quoting their Gramps ID.<br />
<br />
Use your systems "screenshot" function to take any images that may help to explain the problem.<br />
<br />
Here is a sample bug report recording each step taken to reproduce a bug.<br />
<br />
# Create a new database and import "example" data set.<br />
# Click Person View tab.<br />
# Select Martin Smith (Gramps ID I39)<br />
# Click Relationship View tab<br />
# Click the edit button for Hanna Smith (Gramps ID I11)<br />
# In Person Editor for Hanna Smith, doubleclick the birth event<br />
# In Event Editor, change the birth year from 1821 to 1820<br />
# Click OK in Event Editor<br />
# Click OK in Person Editor<br />
# Gramps crashes with the following error:<br />
<br />
Traceback (most recent call last):<br />
File "/home/gramps2/trunk/src/DisplayTabs/_EmbeddedList.py", line 440, in rebuild<br />
self.model = self.build_model(self.get_data(), self.dbstate.db)<br />
File "/home/gramps2/trunk/src/DisplayTabs/_ChildModel.py", line 61, in __init__<br />
child.get_gramps_id(),<br />
AttributeError: 'NoneType' object has no attribute 'get_gramps_id'<br />
<br />
==Bug triage==<br />
<br />
Help the Gramps project [[Bug triage]].<br />
<br />
[[Category:Developers/General]]<br />
[[Category:Developers/Quality Assurance]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=User:Graibeard&diff=70301User:Graibeard2018-09-06T03:54:02Z<p>Graibeard: Bookmarks</p>
<hr />
<div><br />
<br />
One time wikipedia editor (along with thousands of others). Concentrated on the metal working section and then left it when time and life got in the way.<br />
<br />
I'm not a coder but can generally find my way around the simpler stuff.<br />
<br />
I'm familiar with python2, or at least enough to turn out some workable code for weewx. Python3 and Gramps might be a bridge too far though.<br />
<br />
The wiki; I might be able to do something there/here...<br />
<br />
==Bookmarks==<br />
[[Gramps:Media_copyright_tags/All | Media:- copyright tags]]<br />
<br />
[[Category:User|G]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=User:Graibeard&diff=70295User:Graibeard2018-09-05T13:30:47Z<p>Graibeard: Returning user: Add bio, and missing email address?</p>
<hr />
<div><br />
<br />
One time wikipedia editor (along with thousands of others). Concentrated on the metal working section and then left it when time and life got in the way.<br />
<br />
I'm not a coder but can generally find my way around the simpler stuff.<br />
<br />
I'm familiar with python2, or at least enough to turn out some workable code for weewx. Python3 and Gramps might be a bridge too far though.<br />
<br />
The wiki; I might be able to do something there/here...<br />
<br />
[[Category:User|G]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesMarkerColors226.png&diff=793File:EditPreferencesMarkerColors226.png2007-03-06T10:05:21Z<p>Graibeard: </p>
<hr />
<div>Marker Colors tab of Edit->Preferences dialog box, Version 2.2.6<br />
==Licence==<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesGeneral226.png&diff=792File:EditPreferencesGeneral226.png2007-03-06T10:05:07Z<p>Graibeard: </p>
<hr />
<div>General tab of Edit->Preferences dialog box Version 2.2.6<br />
==Licence==<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesDisplay226.png&diff=791File:EditPreferencesDisplay226.png2007-03-06T10:04:44Z<p>Graibeard: </p>
<hr />
<div>Display tab of Edit->Preferences dialog box, Version 2.2.6<br />
==Licence==<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesIDFormats226.png&diff=790File:EditPreferencesIDFormats226.png2007-03-06T10:04:31Z<p>Graibeard: </p>
<hr />
<div>ID Formats tab of Edit->Preferences dialog box, Version 2.2.6<br />
==Licence==<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesNameDisplay226.png&diff=789File:EditPreferencesNameDisplay226.png2007-03-06T10:04:25Z<p>Graibeard: </p>
<hr />
<div>Name Diplay tab of Edit->Preferences dialog box, Version 2.2.6<br />
==Licence==<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesWarnings226.png&diff=788File:EditPreferencesWarnings226.png2007-03-06T10:04:09Z<p>Graibeard: </p>
<hr />
<div>Warnings tab of Edit->Preferences dialog box, Version 2.2.6<br />
==Licence==<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesResearcher226.png&diff=787File:EditPreferencesResearcher226.png2007-03-06T10:04:02Z<p>Graibeard: </p>
<hr />
<div>Researcher tab of Edit->Preferences dialog box, Version 2.2.6<br />
==Licence==<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps:Media_copyright_tags/Free_licenses&diff=785Gramps:Media copyright tags/Free licenses2007-03-06T09:47:36Z<p>Graibeard: /* Any-purpose */ Use <nowiki>{{Free screenshot|GPL}}</nowiki> for Gramps screenshots.</p>
<hr />
<div>=== Any-purpose ===<br />
* {{tl|Attribution}} — Requires attribution<br />
* {{tl|Free screenshot}} — screenshots entirely of free (as in freedom) software. Use <nowiki>{{Free screenshot|GPL}}</nowiki> for Gramps screenshots.<br />
<br />
===Creative Commons===<br />
[[Image:CC some rights reserved.png|right|80px| Creative Commons, some rights reserved.]]<br />
These licenses generally ''require'' that licensees attribute the work as specified by the copyright-holder (licensor).<br />
<br />
* {{tl|cc-by-2.0}} — Attribution 2.0 license.<br />
* {{tl|cc-by-sa-2.5|'''Attribution'''}} — Attribution-Sharealike 2.5 license, with attribution as specified by the ''Attribution'' parameter.<br />
*{{tl|Cc-by-sa-3.0}} - Attribution-Sharealike 3.0 license.<br />
<br />
=== Free Art license (License Art Libre) ===<br />
{{tl|FAL}} — Free Art license ([http://artlibre.org/licence.php/lalgb.html info])<br />
<br />
=== GNU ===<br />
[[Image:Heckert GNU white.png|right|80px| GNU]]<br />
* {{tl|GFDL-self}} — [http://www.gnu.org/copyleft/fdl.html GNU Free Documentation License] (no invariant sections or cover texts)<br />
* {{tl|GPL}} — [http://www.gnu.org/copyleft/gpl.html GNU General Public License]. This tag is designed for GPL images licensed by others (usually as part of a software package). Do not use it to tag images you created yourself. Use another free license, such as {{tl|GFDL-self}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesResearcher226.png&diff=782File:EditPreferencesResearcher226.png2007-03-06T09:29:12Z<p>Graibeard: {{Free screenshot|GPL}}</p>
<hr />
<div>Researcher tab of Edit->Preferences dialog box, Version 2.2.6<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesWarnings226.png&diff=781File:EditPreferencesWarnings226.png2007-03-06T09:29:00Z<p>Graibeard: {{Free screenshot|GPL}}</p>
<hr />
<div>Warnings tab of Edit->Preferences dialog box, Version 2.2.6<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesNameDisplay226.png&diff=780File:EditPreferencesNameDisplay226.png2007-03-06T09:28:54Z<p>Graibeard: {{Free screenshot|GPL}}</p>
<hr />
<div>Name Diplay tab of Edit->Preferences dialog box, Version 2.2.6<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesIDFormats226.png&diff=779File:EditPreferencesIDFormats226.png2007-03-06T09:28:38Z<p>Graibeard: </p>
<hr />
<div>ID Formats tab of Edit->Preferences dialog box, Version 2.2.6<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesDisplay226.png&diff=778File:EditPreferencesDisplay226.png2007-03-06T09:28:32Z<p>Graibeard: {{Free screenshot|GPL}}</p>
<hr />
<div>Display tab of Edit->Preferences dialog box, Version 2.2.6<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesGeneral226.png&diff=777File:EditPreferencesGeneral226.png2007-03-06T09:28:25Z<p>Graibeard: {{Free screenshot|GPL}}</p>
<hr />
<div>General tab of Edit->Preferences dialog box Version 2.2.6<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Screenshots&diff=775Screenshots2007-03-06T09:27:20Z<p>Graibeard: images of tabs in Edit->Preferences dialog box</p>
<hr />
<div>{{stub}}<br />
== Main window ==<br />
Views of the Main window in gramps, following the text links will open a more detailed description.<br />
<gallery><br />
Image:Mainwin.png|[[people screenshot|Person (People)]]<br />
Image:Side-filt.png|[[people screenshot#Main_window, People with filter sidebar|Person View]] with the sidebar filter enabled<br />
Image:Pedigree.png|[[pedigree screenshot|Pedigree]]<br />
Image:Relationship 2 2.png|[[relationships screenshot|Relationships]]<br />
</gallery><br />
<br />
== Edit windows ==<br />
<gallery><br />
Image:Edit-person.png|Edit Person<br />
Image:Edit-media.png|Edit Media Properties<br />
Image:Edit-family.png|Edit Family<br />
Image:Edit-ev-ref.png|Edit Event Reference<br />
</gallery><br />
<br />
==Edit Preferences ==<br />
Tabs in Edit->Preferences dialog box, Version 2.2.6<br />
<gallery><br />
Image:EditPreferencesGeneral226.png|General<br />
Image:EditPreferencesDisplay226.png|Display<br />
Image:EditPreferencesNameDisplay226.png|Name<br />
Image:EditPreferencesIDFormats226.png|ID Formats<br />
Image:EditPreferencesWarnings226.png|Warnings<br />
Image:EditPreferencesResearcher226.png|Researcher<br />
Image:EditPreferencesMarkerColors226.png|Marker Colors<br />
</gallery><br />
<br />
[[Category:screenshots| ]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesMarkerColors226.png&diff=774File:EditPreferencesMarkerColors226.png2007-03-06T09:27:03Z<p>Graibeard: {{Free screenshot|GPL}}</p>
<hr />
<div>Marker Colors tab of Edit->Preferences dialog box, Version 2.2.6<br />
{{Free screenshot|GPL}}</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesMarkerColors226.png&diff=773File:EditPreferencesMarkerColors226.png2007-03-06T09:19:29Z<p>Graibeard: Marker Colors tab of Edit->Preferences dialog box, Version 2.2.6</p>
<hr />
<div>Marker Colors tab of Edit->Preferences dialog box, Version 2.2.6</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesResearcher226.png&diff=772File:EditPreferencesResearcher226.png2007-03-06T09:18:40Z<p>Graibeard: Researcher tab of Edit->Preferences dialog box, Version 2.2.6</p>
<hr />
<div>Researcher tab of Edit->Preferences dialog box, Version 2.2.6</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesWarnings226.png&diff=771File:EditPreferencesWarnings226.png2007-03-06T09:17:53Z<p>Graibeard: Warnings tab of Edit->Preferences dialog box, Version 2.2.6</p>
<hr />
<div>Warnings tab of Edit->Preferences dialog box, Version 2.2.6</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesNameDisplay226.png&diff=770File:EditPreferencesNameDisplay226.png2007-03-06T09:17:06Z<p>Graibeard: Name Diplay tab of Edit->Preferences dialog box, Version 2.2.6</p>
<hr />
<div>Name Diplay tab of Edit->Preferences dialog box, Version 2.2.6</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesIDFormats226.png&diff=769File:EditPreferencesIDFormats226.png2007-03-06T09:14:40Z<p>Graibeard: ID Formats tab of Edit->Preferences dialog box, Version 2.2.6</p>
<hr />
<div>ID Formats tab of Edit->Preferences dialog box, Version 2.2.6</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Tips_for_large_databases&diff=768Tips for large databases2007-03-06T09:13:41Z<p>Graibeard: copyedit, wikilinks and image</p>
<hr />
<div>Large data files, what to do, and what not to do.<br />
<br />
==Loading the file==<br />
[[Image:EditPreferencesGeneral226.png|thumb|General tab of Edit->Preferences dialog box]]<br />
For small files, you can work on GEDCOM or GRAMPS XML format. This works great.<br />
However, these formats are completely loaded in your computer memory so, for larger files, this becomes slow and might bring your computer to a standstill.<br />
<br />
Therefore, you should only handle large files by using the GRAMPS GRDB format. You do this by creating a new GRDB file and importing the large file into it. This can take a long time, so do it in the evenings! If you '''enable database transactions''' in the Edit->Preferences->General menu tab, the importing of data will then be much faster.<br />
<br clear="all"><br />
<br />
== Default view: bookmarks and active person ==<br />
As there are many people, loading the person view might take some time. See a comparison of [[GRAMPS Performance|performance]] on large datasets, between different GRAMPS versions.<br />
<br />
You can circumvent this load time by going to the [[Relationships screenshot|relationships view]] before opening the grdb file. This will open the active person and their family extremely fast, independent of the amount of data you gathered.<br />
<br />
You can add bookmarks to common people, or in the branch you are researching. This allows to change person in the relationships view without the need to activate the person in the person view first.<br />
<br />
== Avoid general filters ==<br />
Filters search all the data looking for the people who satisfy your query. Try to avoid this on large files.<br />
<br />
For name searches do the following:<br />
* click on a person in the [[People screenshot|people view]]. Now start typing the family name of the person you need. The view will automatically go to the family name as you complete your typing.<br />
* for a more detailed search, click ''CTRL-F'' first. This will expand all the nodes and allows to search more specifically.<br />
<br />
== Please contribute ==<br />
If you have more tips for working with large databases, please share them here.<br />
<br />
[[Category:Documentation]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesDisplay226.png&diff=767File:EditPreferencesDisplay226.png2007-03-06T09:06:32Z<p>Graibeard: Display tab of Edit->Preferences dialog box, Version 2.2.6</p>
<hr />
<div>Display tab of Edit->Preferences dialog box, Version 2.2.6</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:EditPreferencesGeneral226.png&diff=762File:EditPreferencesGeneral226.png2007-03-06T08:55:19Z<p>Graibeard: General tab of Edit->Preferences dialog box Version 2.2.6</p>
<hr />
<div>General tab of Edit->Preferences dialog box Version 2.2.6</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Fedora_RPM&diff=581Fedora RPM2007-03-04T10:43:50Z<p>Graibeard: /* Development rpm */ add yum command, fix link</p>
<hr />
<div>The [[installation]] page details how to download and install a working version of '''Gramps''' to your operating system of choice. For most users...<br />
yum install gramps<br />
will be all that is needed for the [http://fedoraproject.org/wiki/ fedora] distribution. This page details a different method and is for those users wanting an alternative version of gramps, this may be to test a SVN version or to install the latest stable version.<br />
<br />
= Development rpm =<br />
It may be possible that the [http://download.fedora.redhat.com/pub/fedora/linux/extras/development/testing rpm] works on the current core version of Fedora. For example, the fc7 rpm will run on fc6, with a few small issues. This usually works, but it is not a supported method, ie: if it breaks the error may not be with gramps or the fedora build, but with the differences between fedora versions. In other words you're on your own with trouble shooting, and if you do report a bug then be sure that it isn't to do with the version mismatch - don't confuse the developers/builders with introduced problems (one's outside their control).<br />
<br />
Assuming you have an existing version of gramps installed, then to install the development rpm for fc6...<br />
yum --enablerepo=extras-development update gramps<br />
<br />
if you don't have any version installed, then '''install''' it using... <br />
yum --enablerepo=extras-development install gramps<br />
<br />
With the release of fc7, extras will apparently no longer exist as a seperate repository. This package will no doubt be found using '''yum --enablerepo=development install gramps''', or similar.<br />
<br />
= To build the rpm from source =<br />
A better approach to installing the binary rpm is to build the package from source, this will build gramps using the package versions that you have installed. The [http://download.fedora.redhat.com/pub/fedora/linux/extras/development/SRPMS/|SRPMS] directory contains the source rpm for the latest development build. Download this rpm, install it and build your own binary using the fedora release (in this case fc6) you're running, as the build environment.<br />
<br />
== To build the rpm as non-root (recommended method) ==<br />
<br />
Install the build environment in the users directory.<br />
'''su -c 'yum install rpmdevtools''''<br />
<br />
Login as a 'normal' user and run '''rpmdev-setuptree''' . This will silently create the 'rpmbuild/' tree in the users home directory (instead of using ''usr/src/redhat'')<br />
<br />
Download the source rpm, for this example it will be <br />
'''wget&nbsp;<nowiki>http://download.fedora.redhat.com/pub/fedora/linux/extras/development/SRPMS/gramps-2.2.4-3.fc7.src.rpm</nowiki>''' or use your browser on the [http://download.fedora.redhat.com/pub/fedora/linux/extras/development/SRPMS/gramps-2.2.4-3.fc7.src.rpm link]<br />
<br />
'''rpmbuild --rebuild gramps-2.2.4-3.fc7.src.rpm''' (additional packages may be required at this step - see ''Problems with the build'' below)<br />
<br />
'''su -c 'yum localinstall /home/<user>/rpmbuild/RPMS/noarch/gramps-2.2.4-3.noarch.rpm'''' (use yum to install the rpm)<br />
<br />
=== Problems with the build ===<br />
The build may abort with an error....<br />
Missing dependencies: These dependencies may be related to the build environment (have you built packages from source, on this machine, before?)<br />
<br />
In addition to the normal build tools, these additional packages are needed to build the gramps rpm: desktop-file-utils, gettext, perl-XML-Parser, gnome-python2-canvas, gnome-python2-gconf, gnome-vfs2-devel, pygtk2-libglade, python-devel, scrollkeeper, and gnome-doc-utils<br />
<br />
Build errors: such as ''unpackaged files'' etc: The remedy for any of these errors will vary depending on circumstances, ie; there are no easy answers. '''Read the error message carefully''', copy a relevant part of the message string, and search the net. The chances are very good that the problem has been encountered before and a solution exists. If that fails and you're still keen, try the [http://sourceforge.net/mail/?group_id=25770|gramps mailing lists.]<br />
<br />
*adding the following line on top of the spec file, /usr/src/redhat//SPEC/gramps.spec: ''%define _unpackaged_files_terminate_build 0'' is a temporary solution provided from the [http://www.rpm.org/hintskinks/unpackaged-files/|rpm.org] lists. Remember, the file will still need packaging, the difference is the build will complete, or the next error will abort it. You'll just be a step closer to knowing how to fix it, or phrasing the question ;-)<br />
<br />
= To build an rpm from SVN =<br />
<br />
'''Caveat emptor:'''<br />
<br />
*Some assumptions have been made here, the prime one being that you have any needed devel packages installed, and therefore a system that can actually build from source. If you don't have one - yet - then continue on and hopefully your system will give enough clues so that you can get to the final stage, and build an rpm. (Ah! and please update this page to suit, or notify the mailing list).<br />
*A secondary assumption is that your happy to install '''over''' your existing gramps installation? This is the SVN (bleeding edge) package and things may break. The flip side to that problem is that once they're reported they'll be fixed and goodness will prevail!<br />
*And with that in mind, '''backup''' your database first. '''Don't work on that which is irreplacable.''' <br />
**Happy Bug Hunting!<br />
<br />
If this is the first build on this machine then the following installation may be required, to install the build environment in the users directory.<br />
'''su -c 'yum install rpmdevtools''''<br />
<br />
then login as a 'normal' user and run '''rpmdev-setuptree''' . This will silently create the 'rpmbuild/' tree in the users home directory (instead of using ''usr/src/redhat''). In addition the dependencies listed above (under 'Problems with the build' need to be installed. Once this is done the gramps build can proceed.<br />
<br />
The following acts out the build process for the 2.2.5 pre-release from SVN.<br />
<br />
'''svn co https://svn.sourceforge.net/svnroot/gramps/trunk/gramps2 '''<br />
<br />
'''mv gramps2 gramps-2.2.5 && cd gramps-2.2.5'''<br />
<br />
'''./autogen.sh'''<br />
<br />
If this fails with ''which: no gnome-autogen.sh '' follow the advice and execute <br />
'''su -c 'yum -y install gnome-common''''<br />
<br />
If it again fails, but with...<br />
<pre><br />
checking for intltool >= 0.25...<br />
testing intltoolize... not found.<br />
...<br />
...<br />
...<br />
Checking for forbidden M4 macros...<br />
***Error***: some autoconf macros required to build gramps<br />
were not found in your aclocal path, or some forbidden<br />
macros were found. Perhaps you need to adjust your<br />
ACLOCAL_FLAGS?<br />
</pre><br />
then '''su -c 'yum -y install intltool''''<br />
<br />
In my case this succesfully ran to completion, except for the following suggestion<br />
<pre><br />
Please add the files<br />
codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4<br />
progtest.m4<br />
from the /usr/share/aclocal directory to your autoconf macro directory<br />
or directly to your aclocal.m4 file.<br />
You will also need config.guess and config.sub, which you can get from<br />
ftp://ftp.gnu.org/pub/gnu/config/.<br />
</pre><br />
which I have so far ignored, with no ill effects.<br />
<br />
The resulting directory now needs to be packaged as gramps-2.2.5.tar.gz<br />
<br />
'''cd ../'''<br />
<br />
'''tar cvf - gramps-2.2.5 | gzip -f9 > gramps-2.2.5.tar.gz'''<br />
<br />
'''mv gramps-2.2.5.tar.gz /home/<user>/rpmbuild/SOURCES/'''<br />
<br />
'''cd /home/<user>/rpmbuild/'''<br />
<br />
'''su -c 'rpmbuild -bb SPECS/gramps.spec'''' where gramps spec is the following file.<br />
<br />
But first a word about the spec file, this one works for 2.2.4 and 2.2.5 on fedora core 6, it may not work on other versions/releases - whatever. If it doesn't see above (ie: don't despair, go looking and try to solve the problem, if you succeed then modify the spec - both yours and the one on this page - to suit. If you don't succeed, then ask as per the suggestion above.)<br />
This spec file is a minor adaption of the one used by the fedora extras maintainers and has been extracted from the source file ''gramps-2.2.4-3.fc7.src.rpm''. There may be a more up todate file in a newer src package?<br />
<br />
<pre><br />
Name: gramps<br />
Version: 2.2.5<br />
Release: 1%{?dist}<br />
Summary: Genealogical Research and Analysis Management Programming System<br />
<br />
Group: Applications/Productivity<br />
License: GPL<br />
URL: http://gramps.sourceforge.net/<br />
Source0: http://download.sourceforge.net/%{name}/%{name}-%{version}.tar.gz<br />
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)<br />
BuildArch: noarch<br />
<br />
BuildRequires: desktop-file-utils<br />
BuildRequires: gettext<br />
BuildRequires: perl(XML::Parser)<br />
BuildRequires: gnome-python2-canvas<br />
BuildRequires: gnome-python2-gconf<br />
BuildRequires: gnome-vfs2-devel<br />
BuildRequires: pygtk2-libglade<br />
BuildRequires: python-devel<br />
BuildRequires: scrollkeeper<br />
BuildRequires: gnome-doc-utils<br />
<br />
Requires: gnome-python2-canvas<br />
Requires: gnome-python2-gconf<br />
Requires: gnome-python2-gnomevfs<br />
Requires: gnome-python2<br />
Requires: gnome-python2-gnomeprint<br />
Requires: gnome-python2-gtkspell<br />
Requires: ImageMagick<br />
Requires: freefont<br />
Requires: pygtk2<br />
Requires: pygtk2-libglade<br />
Requires: rcs<br />
Requires: python-reportlab<br />
Requires: graphviz<br />
<br />
Requires(pre): GConf2<br />
Requires(post): desktop-file-utils<br />
Requires(post): scrollkeeper<br />
Requires(post): GConf2<br />
Requires(preun): GConf2<br />
Requires(postun): desktop-file-utils<br />
Requires(postun): scrollkeeper<br />
<br />
<br />
%description<br />
gramps (Genealogical Research and Analysis Management Programming<br />
System) is a GNOME based genealogy program supporting a Python<br />
based plugin system.<br />
<br />
<br />
%prep<br />
%setup -q<br />
<br />
<br />
%build<br />
%configure --disable-schemas-install --disable-scrollkeeper --disable-mime-install<br />
make<br />
<br />
<br />
%install<br />
rm -rf ${RPM_BUILD_ROOT}<br />
%makeinstall GNOME_DATADIR="${RPM_BUILD_ROOT}%{_datadir}"<br />
#Remove duplicate doc<br />
rm -f ${RPM_BUILD_ROOT}%{_datadir}/%{name}/COPYING<br />
<br />
mkdir -p $RPM_BUILD_ROOT%{_datadir}/icons/hicolor/48x48/apps/<br />
cp -p $RPM_BUILD_ROOT%{_datadir}/%{name}/images/%{name}.png $RPM_BUILD_ROOT%{_datadir}/icons/hicolor/48x48/apps/<br />
<br />
%find_lang %{name}<br />
<br />
desktop-file-install --vendor fedora --delete-original \<br />
--dir ${RPM_BUILD_ROOT}%{_datadir}/applications \<br />
${RPM_BUILD_ROOT}%{_datadir}/applications/%{name}.desktop<br />
<br />
<br />
%clean<br />
rm -rf ${RPM_BUILD_ROOT}<br />
<br />
<br />
%pre<br />
if [ "$1" -gt 1 ]; then<br />
export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source`<br />
gconftool-2 --makefile-uninstall-rule \<br />
%{_sysconfdir}/gconf/schemas/%{name}.schemas >/dev/null || :<br />
fi<br />
<br />
<br />
%post<br />
export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source`<br />
gconftool-2 --makefile-install-rule \<br />
%{_sysconfdir}/gconf/schemas/%{name}.schemas > /dev/null || :<br />
scrollkeeper-update -q -o %{_datadir}/omf/%{name} || :<br />
update-desktop-database &> /dev/null ||:<br />
update-mime-database %{_datadir}/mime &> /dev/null || :<br />
touch --no-create %{_datadir}/icons/hicolor || :<br />
%{_bindir}/gtk-update-icon-cache --quiet %{_datadir}/icons/hicolor || :<br />
<br />
<br />
%preun<br />
if [ "$1" -eq 0 ]; then<br />
export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source`<br />
gconftool-2 --makefile-uninstall-rule \<br />
%{_sysconfdir}/gconf/schemas/%{name}.schemas > /dev/null || :<br />
fi<br />
<br />
<br />
%postun<br />
scrollkeeper-update -q || :<br />
update-desktop-database &> /dev/null ||:<br />
update-mime-database %{_datadir}/mime &> /dev/null || :<br />
touch --no-create %{_datadir}/icons/hicolor || :<br />
%{_bindir}/gtk-update-icon-cache --quiet %{_datadir}/icons/hicolor || :<br />
<br />
<br />
%files -f %{name}.lang<br />
%defattr(-,root,root,-)<br />
%doc AUTHORS COPYING COPYING-DOCS FAQ NEWS TODO<br />
%{_bindir}/%{name}<br />
%{_datadir}/%{name}/<br />
%{_datadir}/applications/fedora-%{name}.desktop<br />
%{_datadir}/application-registry/%{name}.applications<br />
%{_datadir}/omf/%{name}/<br />
%{_datadir}/mime/packages/%{name}.xml<br />
%{_datadir}/mime-info/*<br />
%{_datadir}/icons/hicolor/48x48/apps/%{name}.png<br />
%{_datadir}/icons/gnome/48x48/mimetypes/*.png<br />
%{_datadir}/icons/gnome/scalable/mimetypes/*.svg<br />
%{_datadir}/pixmaps/%{name}.png<br />
%{_sysconfdir}/gconf/schemas/%{name}.schemas<br />
%{_mandir}/man1/%{name}.1.gz<br />
%{_datadir}/gnome/help/%{name}/<br />
<br />
<br />
%changelog<br />
* Wed Dec 27 2006 Brian Pepple <bpepple@fedoraproject.org> - 2.2.4-3<br />
- Add requires on gnome-python2-gtkspell & freefont.<br />
<br />
* Tue Dec 26 2006 Brian Pepple <bpepple@fedoraproject.org> - 2.2.4-2<br />
- Add gramp.png to files.<br />
<br />
* Tue Dec 26 2006 Brian Pepple <bpepple@fedoraproject.org> - 2.2.4-1<br />
- Update to 2.2.4.<br />
<br />
* Fri Dec 8 2006 Brian Pepple <bpepple@fedoraproject.org> - 2.2.3-2<br />
- Rebuild against new python.<br />
<br />
* Mon Nov 27 2006 Brian Pepple <bpepple@fedoraproject.org> - 2.2.3-1<br />
- Update to 2.2.3.<br />
- Add scalable mimetype icons to files section.<br />
<br />
* Sat Nov 4 2006 Brian Pepple <bpepple@fedoraproject.org> - 2.2.2-1<br />
- Update to 2.2.2.<br />
- Add scriptlet for gtk+ icon cache.<br />
- Disable scrollkeeper & mime-install in configure.<br />
- Simplify files since we are no longer ghosting *.pyo files.<br />
- Drop X-Fedora desktop category.<br />
- Add BR on gnome-doc-utils.<br />
<br />
* Wed Sep 6 2006 Brian Pepple <bpepple@fedoraproject.org> - 2.0.11-5<br />
- Don't ghost *.pyo files.<br />
<br />
* Sat Sep 2 2006 Brian Pepple <bpepple@fedoraproject.org> - 2.0.11-4<br />
- Rebuild for FC6.<br />
- Remove requires on python, it's no longer needed.<br />
- Use --disable-schemas-install to config.<br />
- Add BR for perl(XML::Parser).<br />
<br />
* Mon May 1 2006 Brian Pepple <bdpepple@ameritech.net> - 2.0.11-3<br />
- Update to 2.0.11.<br />
- Drop INSTALL, README & ChangeLog documentation.<br />
- Ghost .pyo files.<br />
<br />
* Sat Mar 11 2006 Brian Pepple <bdpepple@ameritech.net> - 2.0.10-3<br />
- Remove Utility category from desktop file.<br />
- Update scriptlets.<br />
<br />
* Tue Feb 28 2006 Brian Pepple <bdpepple@ameritech.net> - 2.0.10-2<br />
- Update to 2.0.10.<br />
<br />
* Thu Feb 16 2006 Brian Pepple <bdpepple@ameritech.net> - 2.0.9-6<br />
- Remove unnecessary BR (gnome-python2-gnomevfs, pygtk2, gnome-python2, GConf2). <br />
<br />
* Mon Feb 13 2006 Brian Pepple <bdpepple@ameritech.net> - 2.0.9-5<br />
- rebuilt for new gcc4.1 snapshot and glibc changes<br />
<br />
* Sat Jan 28 2006 Brian Pepple <bdpepple@ameritech.net> - 2.0.9-4<br />
- Add require for shared-mime-info.<br />
- Remove mime.cache.<br />
- Use python-abi.<br />
<br />
* Wed Dec 14 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.9-3<br />
- Add requires for gnome-python2-gnomeprint.<br />
<br />
* Tue Dec 13 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.9-2<br />
- Make noarch. (#170974)<br />
- Update to 2.0.9.<br />
<br />
* Wed Sep 7 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.8-2<br />
- Update to 2.0.8.<br />
<br />
* Wed Aug 17 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.6-3<br />
- Specify ver for python-reportlab.<br />
<br />
* Mon Aug 15 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.6-2<br />
- Update to 2.0.6.<br />
- Bump minimum ver for python.<br />
- Add requires for python-reportlab & graphviz for reports.<br />
<br />
* Wed Jul 6 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.5-1<br />
- Update to 2.0.5.<br />
<br />
* Wed Jun 29 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.4-1<br />
- Update to 2.0.4.<br />
<br />
* Sat Jun 18 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.3-1<br />
- Update to 2.0.3.<br />
- Add dist tag.<br />
<br />
* Sat May 21 2005 Brian Pepple <bdpepple@ameritech.net> - 2.0.0-1<br />
- Update to 2.0.0.<br />
- Add mime info.<br />
- Use more macros.<br />
<br />
* Fri Apr 7 2005 Michael Schwendt <mschwendt[AT]users.sf.net><br />
- rebuilt<br />
<br />
* Sun Feb 06 2005 Phillip Compton <pcompton[AT]proteinmedia.com - 1.0.10-1<br />
- 1.0.10.<br />
<br />
* Sun Nov 28 2004 Phillip Compton <pcompton[AT]proteinmedia.com - 1.0.8-3<br />
- Version bump.<br />
<br />
* Sat Nov 13 2004 Phillip Compton <pcompton[AT]proteinmedia.com - 1.0.8-0.fdr.2<br />
- Spec cleanup.<br />
<br />
* Sat Nov 06 2004 Phillip Compton <pcompton[AT]proteinmedia.com - 1.0.8-0.fdr.1<br />
- 1.0.8.<br />
<br />
* Wed Aug 18 2004 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:1.0.7-0.fdr.1<br />
- Update to 1.0.7.<br />
<br />
* Sat Jul 31 2004 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:1.0.5-0.fdr.1<br />
- Update to 1.0.5.<br />
<br />
* Wed Jul 21 2004 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:1.0.4-0.fdr.1<br />
- Update to 1.0.4.<br />
<br />
* Thu Apr 22 2004 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:1.0.3-0.fdr.1<br />
- Update to 1.0.3.<br />
<br />
* Tue Apr 20 2004 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:1.0.2-0.fdr.2<br />
- Dropped unneccessary BuildReqs.<br />
- Removed Requires(foo,bar) notation.<br />
<br />
* Tue Apr 13 2004 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:1.0.2-0.fdr.1<br />
- Update to 1.0.2.<br />
- Using upstream desktop entry.<br />
<br />
* Sat Feb 28 2004 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:1.0.1.0-0.fdr.1<br />
- Update to 1.0.1.<br />
<br />
* Mon Jan 12 2004 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:0.98.0-0.fdr.1<br />
- Update to 0.98.0.<br />
<br />
* Sat Nov 22 2003 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:0.95-0.fdr.5<br />
- dropped smp_mflags.<br />
<br />
* Fri Nov 21 2003 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:0.95-0.fdr.4<br />
- Req gnome-python2.<br />
<br />
* Mon Nov 17 2003 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:0.95-0.fdr.3<br />
- BuildReq gnome-python2.<br />
<br />
* Mon Nov 10 2003 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:0.95-0.fdr.2<br />
- Modifications to desktop entry.<br />
- Reqs ImageMagick and rcs.<br />
<br />
* Fri Oct 10 2003 Phillip Compton <pcompton[AT]proteinmedia.com> - 0:0.95-0.fdr.1<br />
- Initial RPM release.<br />
</pre><br />
<br />
To install the succesful build, <br />
<br />
'''su -c 'yum localinstall /home/<user>/rpmbuild/RPMS/noarch/gramps-2.2.5-1.noarch.rpm''''<br />
<br />
or perhaps use localupdate? (see '''man yum''')<br />
<br />
'''su -c 'yum localupdate /home/<user>/rpmbuild/RPMS/noarch/gramps-2.2.5-1.noarch.rpm''''<br />
<br />
To bypass the signing process, '''temporarily''' change the contents of ''/etc/yum.conf'' to disable (0) the gpgcheck.<br />
<pre><br />
#gpgcheck=1<br />
gpgcheck=0<br />
</pre><br />
and restore the file to its original state when finished.<br />
<br />
= See also =<br />
<br />
An alternative? spec file [http://svn.rpmforge.net/svn/trunk/rpms/gramps/gramps.spec dags spec - 2.2.3]<br />
<br />
To rpmbuild as non root<br />
[http://fedoranews.org/tchung/rpmbuild/ HOWTO: How to create rpmbuild directory], and [http://myy.helia.fi/~karte/linux/doc/rpm-build-as-user.html RPM Building as a User]<br />
<br />
<br />
[[Category:Developers/Tutorials]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Installation&diff=580Installation2007-03-04T10:07:29Z<p>Graibeard: reorder with live CD first, distros next</p>
<hr />
<div>==Live CD==<br />
If you are interested in GRAMPS, but are afraid to actually install it or unable to install it (not your PC, windows, no internet at home, work laptop, ...), then try out our [[Linux Genealogy CD]]. It runs without installing on the hard disk and contains a collection of open source, free, genealogy programs. You can then install [http://ubuntu.com Ubuntu 6.06 LTS] and GRAMPS from the CD anytime you like.<br />
<br />
==Easy download and install of GRAMPS 2.2.6==<br />
Before downloading, check if the version of GRAMPS in your distribution is not current:<br />
* Debian, (K,X,Edu)Ubuntu, Mepis, Suse: <code><br />
apt-get install gramps</code><br />
* Fedora: <code><br />
yum install gramps</code><br />
==Upgrading to the latest version==<br />
If your version of GRAMPS is not current, some users offer up to date packages for some distributions:<br />
<br />
* '''Ubuntu''': On sourceforge, [http://sourceforge.net/project/showfiles.php?group_id=25770 download] gramps_zzz.deb and gramps-help_zzz.deb, and install with your package manager.<br />
* '''SuSE''': Richard Bos has been providing the GRAMPS releases for SuSE's apt repository. They are always last release in [http://software.opensuse.org/download/home:/rbos/ his repository]. See also [http://www.suseforums.net/index.php?s=22f80a050a1e3cffffd590db0813dea9&showtopic=28727&pid=152093&st=0&#entry152093. this forum entry].<br />
* '''Mandriva''': Packages for Mandriva are available for use with urpmi from [http://seerofsouls.com/ SeerOfSouls.com].<br />
* '''Fedora''': The alternative to installing from source (described below) is to [[fedora rpm|build a package]] from an rpm spec file, or install a binary from fedora testing.<br />
* '''Debian''': the latest version is installed directly into unstable and can be upgraded from your package manager. Testing is updated 10 days later (except near a new stable release).<br />
<br />
''Note: Some Linux distributions may have a slightly different way to download and install packages for GRAMPS. Please read the installation instructions specific to your distribution before downloading.''<br />
<br />
In all other cases, you must [http://sourceforge.net/project/showfiles.php?group_id=25770 download] the source package zzz.tar.gz, and install GRAMPS manually. See below for details.<br />
<br />
==Windows, BSD, MacOs, Solaris==<br />
For Windows, there is an experimental [[Windows installer]]. For more recent versions of GRAMPS in Windows, you need to wait untill a new installer is made available.<br />
<br />
For BSD, MacOS, Solaris there are experimental install instructions below.<br />
<br />
==Gnome and KDE==<br />
You can use both, but GRAMPS fits in better with GNOME. For KDE there are some minor issues due to some (GTK) issues outside of GRAMPS. Check the [[KDE page]] to know what these problems might be.<br />
<br />
=Additional software GRAMPS can benefit from=<br />
GRAMPS does not rely on the following programs, however, having them will increase your productivity:<br />
<br />
* '''Gnome-print''': It adds the ability to directly print, to preview, and to generate fully internationalized PS and PDF output. At this time, one needs to install gnome-python-desktop to obtain this package (it might be known under different names, eg on debian python-gnome2-desktop).<br />
* '''Spell checking''': Installing python-gnome2-extras provides the gtkspell module, which adds spell checking in the notes<br />
* '''Graphviz''', '''Inkscape''': Gramps can make nice Genealogical trees (relationship graphs). These are generated by the Graphviz package, which defines a code (dot), as well as programs to produce graphs (dotty, to be called from command line). This gives you as researcher most power over how your tree will look, but has a learning curve. An alternative is to make a graphical report, converting the tree to an svg file, which you then can open/edit/refine in eg Inkscape.<br />
* '''ttf-freefont''': Useful as a font that supports a large subset of the unicode and is a true type. This works well with both gnomeprint and graphviz output.<br />
<br />
Other packages might also be usefull:<br />
<br />
* '''Yelp''': Gnome help browser. This allows to call and read the GRAMPS documentation on your computer.<br />
<br />
=Installing from source=<br />
==General Requirements==<br />
<br />
GRAMPS 2.0 requires python 2.3 and the gnome-python and pygtk2 packages. The gnome-python module should be 2.6.0 or greater. The pygtk package should be version 2.5.0 or greater.<br />
<br />
==Obtaining the source==<br />
<br />
* The lastest stable version of GRAMPS can be downloaded from the [http://sourceforge.net/projects/gramps GRAMPS SourceForge page]. As of this writing, this is gramps-2.2.6.tar.gz. Extract this file into a directory: <code><br />
tar xzvf gramps-zzz.tar.gz<br />
</code> and then go into this directory:<code><br />
cd gramps-zzz<br />
</code><br />
* If you are interested in testing out the latest development version of GRAMPS, it can be obtained from SVN, see [[Brief introduction to SVN]]. The SVN version of GRAMPS is potentially very dangerous as it has not been extensively tested. It may be prone to crashing and cause extensive data loss. Please use with caution.<br />
<br />
Please, now is the time to read the INSTALL and README files accompanying the code. They come with the most recent information.<br />
<br />
==Installing from source code on Linux==<br />
<br />
GRAMPS provides a script that can be used to prepare the code for building. This script automatically calls the standard configure script:<code><br />
./autogen.sh</code><br />
<br />
This script will report any missing dependencies. Install these (see also INSTALL file). Building from source code typically requires that the development versions of the required libraries be installed. You might consider setting a prefix path with autogen.sh, see the INSTALL file for instructions. Standard install is in<br />
<br />
Once a successful run of autogen.sh has been completed, you can run the typical make procedure.<code><br />
make<br />
make install</code><br />
<br />
==Installing from source code on BSD==<br />
<br />
Installing on BSD is as straithforward as on linux, apart from some minor issues like tools having different names. See the [[BSD page]] for details.<br />
<br />
==Installing from source code on Mac OS X==<br />
<br />
Some users have successfully installed GRAMPS on Mac OS X. See the [[Mac OS X]] page for details. Please, add to the wiki if you successfully installed GRAMPS on OS X.<br />
<br />
==Installing from source code on Windows==<br />
<br />
Due to the dependencies, it is difficult to install GRAMPS on Windows. Fortunately some users have made an installer hiding all these details. See the [[Windows installer]] page for details. Use this at your own risk! The developers of GRAMPS provide the space for this install page, but are not responsible for it!<br />
<br />
==Installing from source code on Solaris==<br />
<br />
Previous versions of GRAMPS have run on Solaris. No recent cases are know to us however. Should you have successfully installed GRAMPS on solaris, please update the [[Solaris page]].<br />
<br />
[[Category:Documentation]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Linux_Genealogy_CD&diff=579Linux Genealogy CD2007-03-04T10:04:36Z<p>Graibeard: redirect Ubuntu 6.06 link, add various ext links and image, mv cat: to the bottom</p>
<hr />
<div>[[Image:cdlabel_web_l.jpg|right]]<br />
The Linux Genealogy Desktop CD 2.0 has been released June 2, 2006. It has been [http://blog.eogn.com/eastmans_online_genealogy/2006/07/linux_genealogy.html reviewed] by Dick Eastman in his [http://eogn.com/ Online Genealogy Newsletter].<br />
<br />
This Live CD is based on [http://old-releases.ubuntu.com/releases/6.06.0/ Ubuntu 6.06 (Dapper Drake)] Desktop CD and, in addition to the regular Dapper, features pre-installed '''GRAMPS''', [http://geneweb.sourceforge.net/ GeneWeb], and [http://lifelines.sourceforge.net/ LifeLines] applications, as well as the [http://www.graphviz.org/ GraphViz] program to draw pretty graphs in GRAMPS. The CD is available only for the x86 architecture.<br />
<br />
In contrast with the previous release, this disk also allows permanent installation of Linux and genealogical software on your computer's hard drive. This way you achieve adequate speed and the ability to save your data, and can do real work with your Linux software. Everything is similar to the Live Session, except that this is a permanent setup.<br />
==Obtaining the CD==<br />
The disk can be obtained via a number of ways.<br />
* Centralized download. Thanks to the hosting opportunity donated to us, the CD images can be downloaded via [http://ftp.gwdg.de/pub/linux/gramps/ http], [ftp://ftp.gwdg.de/pub/linux/gramps/ ftp], or rsync (rsync://ftp.gwdg.de/pub/linux/gramps/) protocols.<br />
* BitTorrent download. Use these files to download and verify the CD image via BitTorrent: [http://www.gramps-project.org/files/lgenealogy-2.0-desktop-i386.iso.torrent torrent file], [http://www.gramps-project.org/files/lgenealogy-2.0-desktop-i386.iso.md5sum its md5sum], and [http://www.gramps-project.org/files/lgenealogy-2.0-desktop-i386.iso.md5sum.gpg its gpg signature]. Please keep in mind that the torrent downloads are provided by a few kind souls from their personal computers and that the speed and the very availability of the torrents depends entirely on them.<br />
* Purchase disks. An alternative to downloading the image is by purchasing the physical CDs. The CDs are currently available for purchase in [http://www.cdfhs-aus.com/catalog/index.php Australia] and [http://store.roitman.org/ the USA].<br />
<br />
[[Category:Documentation]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=File:Cdlabel_web_l.jpg&diff=578File:Cdlabel web l.jpg2007-03-04T10:00:20Z<p>Graibeard: Image taken from...
http://gramps-project.org/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=19&MMN_position=33:9
I'm assuming it's licensed appropriately, but will leave to others to label accordingly.</p>
<hr />
<div>Image taken from...<br />
http://gramps-project.org/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=19&MMN_position=33:9<br />
<br />
I'm assuming it's licensed appropriately, but will leave to others to label accordingly.</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Screenshots&diff=577Screenshots2007-03-04T09:10:34Z<p>Graibeard: a space, take 2</p>
<hr />
<div>{{stub}}<br />
== Main window ==<br />
Views of the Main window in gramps, following the text links will open a more detailed description.<br />
<gallery><br />
Image:Mainwin.png|[[people screenshot|Person (People)]]<br />
Image:Side-filt.png|[[people screenshot#Main_window, People with filter sidebar|Person View]] with the sidebar filter enabled<br />
Image:Pedigree.png|[[pedigree screenshot|Pedigree]]<br />
Image:Relationship 2 2.png|[[relationships screenshot|Relationships]]<br />
</gallery><br />
<br />
== Edit windows ==<br />
<gallery><br />
Image:Edit-person.png|Edit Person<br />
Image:Edit-media.png|Edit Media Properties<br />
Image:Edit-family.png|Edit Family<br />
Image:Edit-ev-ref.png|Edit Event Reference<br />
</gallery><br />
<br />
[[Category:screenshots| ]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Screenshots&diff=576Screenshots2007-03-04T09:08:55Z<p>Graibeard: hmm, better with a space</p>
<hr />
<div>{{stub}}<br />
== Main window ==<br />
Views of the Main window in gramps, following the text links will open a more detailed description.<br />
<gallery><br />
Image:Mainwin.png|[[people screenshot|Person (People)]]<br />
Image:Side-filt.png|[[people screenshot#Main_window, People with filter sidebar|Person View]] with the sidebar filter enabled<br />
Image:Pedigree.png|[[pedigree screenshot|Pedigree]]<br />
Image:Relationship 2 2.png|[[relationships screenshot|Relationships]]<br />
</gallery><br />
<br />
== Edit windows ==<br />
<gallery><br />
Image:Edit-person.png|Edit Person<br />
Image:Edit-media.png|Edit Media Properties<br />
Image:Edit-family.png|Edit Family<br />
Image:Edit-ev-ref.png|Edit Event Reference<br />
</gallery><br />
<br />
[[Category:screenshots|screenshots]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Screenshots&diff=575Screenshots2007-03-04T09:07:33Z<p>Graibeard: adjust to be first in category</p>
<hr />
<div>{{stub}}<br />
== Main window ==<br />
Views of the Main window in gramps, following the text links will open a more detailed description.<br />
<gallery><br />
Image:Mainwin.png|[[people screenshot|Person (People)]]<br />
Image:Side-filt.png|[[people screenshot#Main_window, People with filter sidebar|Person View]] with the sidebar filter enabled<br />
Image:Pedigree.png|[[pedigree screenshot|Pedigree]]<br />
Image:Relationship 2 2.png|[[relationships screenshot|Relationships]]<br />
</gallery><br />
<br />
== Edit windows ==<br />
<gallery><br />
Image:Edit-person.png|Edit Person<br />
Image:Edit-media.png|Edit Media Properties<br />
Image:Edit-family.png|Edit Family<br />
Image:Edit-ev-ref.png|Edit Event Reference<br />
</gallery><br />
<br />
[[Category:screenshots|*]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_People_Category_screenshots&diff=574Gramps People Category screenshots2007-03-04T09:06:47Z<p>Graibeard: /* Main window, People */ line break</p>
<hr />
<div>__TOC__<br />
== Main window, People ==<br />
This screenshot shows the main window in GRAMPS, displaying the Person (People) View. <br />
<br />
This view shows all people in the database, displayed in a tree and grouped by family name. The view may be switched to other views by selecting one of the buttons on the lefthand side of the screen.<br />
<br />
[[Image:Mainwin.png|Main window (Person View)]]<br />
<br />
== Main window, People with filter sidebar ==<br />
This screenshot shows the same view, but with the sidebar filter enabled. The filter allows you to control which people in the display are visible in the display.<br />
<br />
[[Image:Side-filt.png|Main window with the sidebar filter enabled]]<br />
<br />
[[Category:screenshots]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_Relationships_Category_view_screenshot&diff=573Gramps Relationships Category view screenshot2007-03-04T09:05:36Z<p>Graibeard: minimal description, full size image</p>
<hr />
<div>== Main window, Relationships ==<br />
This [[screenshot]] shows the main window in GRAMPS, displaying the Relationships View. <br />
<br />
[[Image:Relationship 2 2.png|Relationships view]]<br />
<br />
[[Category:screenshots]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Screenshot&diff=572Screenshot2007-03-04T09:04:53Z<p>Graibeard: #REDIRECT screenshots</p>
<hr />
<div>#REDIRECT [[screenshots]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_Charts_Category_Pedigree_view_screenshot&diff=571Gramps Charts Category Pedigree view screenshot2007-03-04T08:54:38Z<p>Graibeard: +Category:screenshots</p>
<hr />
<div>== Main window, Pedigree view ==<br />
This screenshot shows the main window in GRAMPS, displaying the Pedigree (People) View.<br />
<br />
This shot shows the tree as ''Tree style, Version A'' and displaying ''4 generations'' These defaults may be changed while running Gramps, by right clicking the Pedigree window background, obtaining the pop-up menu and then selecting the appropriate option, tree style or number of generations.<br />
<br />
[[Image:Pedigree.png|Pedigree view (version 2.2.4 and above)]]<br />
<br />
[[Category:screenshots]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Category:Screenshots&diff=570Category:Screenshots2007-03-04T08:53:58Z<p>Graibeard: token description!</p>
<hr />
<div>Screenshots of all gramps windows</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_Charts_Category_Pedigree_view_screenshot&diff=569Gramps Charts Category Pedigree view screenshot2007-03-04T08:53:04Z<p>Graibeard: description with full size image.</p>
<hr />
<div>== Main window, Pedigree view ==<br />
This screenshot shows the main window in GRAMPS, displaying the Pedigree (People) View.<br />
<br />
This shot shows the tree as ''Tree style, Version A'' and displaying ''4 generations'' These defaults may be changed while running Gramps, by right clicking the Pedigree window background, obtaining the pop-up menu and then selecting the appropriate option, tree style or number of generations.<br />
<br />
[[Image:Pedigree.png|Pedigree view (version 2.2.4 and above)]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_People_Category_screenshots&diff=568Gramps People Category screenshots2007-03-04T08:32:55Z<p>Graibeard: /* Main window, People with filter sidebar */ + Category:screenshots</p>
<hr />
<div>__TOC__<br />
== Main window, People ==<br />
This screenshot shows the main window in GRAMPS, displaying the Person (People) View. This view shows all people in the database, displayed in a tree and grouped by family name. The view may be switched to other views by selecting one of the buttons on the lefthand side of the screen.<br />
<br />
[[Image:Mainwin.png|Main window (Person View)]]<br />
<br />
<br />
== Main window, People with filter sidebar ==<br />
This screenshot shows the same view, but with the sidebar filter enabled. The filter allows you to control which people in the display are visible in the display.<br />
<br />
[[Image:Side-filt.png|Main window with the sidebar filter enabled]]<br />
<br />
[[Category:screenshots]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Screenshots&diff=567Screenshots2007-03-04T08:31:55Z<p>Graibeard: continue formatting as gallery, link to fuller descriptions</p>
<hr />
<div>{{stub}}<br />
== Main window ==<br />
Views of the Main window in gramps, following the text links will open a more detailed description.<br />
<gallery><br />
Image:Mainwin.png|[[people screenshot|Person (People)]]<br />
Image:Side-filt.png|[[people screenshot#Main_window, People with filter sidebar|Person View]] with the sidebar filter enabled<br />
Image:Pedigree.png|[[pedigree screenshot|Pedigree]]<br />
Image:Relationship 2 2.png|[[relationships screenshot|Relationships]]<br />
</gallery><br />
<br />
== Edit windows ==<br />
<gallery><br />
Image:Edit-person.png|Edit Person<br />
Image:Edit-media.png|Edit Media Properties<br />
Image:Edit-family.png|Edit Family<br />
Image:Edit-ev-ref.png|Edit Event Reference<br />
</gallery><br />
<br />
[[Category:screenshots]]</div>Graibeardhttps://gramps-project.org/wiki/index.php?title=Gramps_People_Category_screenshots&diff=566Gramps People Category screenshots2007-03-04T08:21:39Z<p>Graibeard: description with full size image, People and People with sidebar</p>
<hr />
<div>__TOC__<br />
== Main window, People ==<br />
This screenshot shows the main window in GRAMPS, displaying the Person (People) View. This view shows all people in the database, displayed in a tree and grouped by family name. The view may be switched to other views by selecting one of the buttons on the lefthand side of the screen.<br />
<br />
[[Image:Mainwin.png|Main window (Person View)]]<br />
<br />
<br />
== Main window, People with filter sidebar ==<br />
This screenshot shows the same view, but with the sidebar filter enabled. The filter allows you to control which people in the display are visible in the display.<br />
<br />
[[Image:Side-filt.png|Main window with the sidebar filter enabled]]</div>Graibeard