You can find the .spec-file and sources prepared for building at https://github.com/htgoebel/freeplane-mageia

*** Bug 10265 has been marked as a duplicate of this bug. ***

CC: (none) => isolde

Hi Hartmut! Why not join Mageia as a packager apprentice so that you could maintain Freeplane yourself? I see from your github page that you have done a lot already to prepare it.

https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

Severity: normal => enhancement

Hi Samuel, the main reason is: I'm not a Java developer but a Python developer. And I do not want to end with maintaining several Java packages where I do not have much clue about Java specials. If there would be somebody helping me to get the current packages to release-quality level, it should be easy to keep them up. But when I asked for support on the dev-list, there was not much response.

I have found a rmp for Rosa. But I like besser en mageia'rpm !

CC: (none) => liste

Freeplane was imported in Cauldron by AlexL: http://svnweb.mageia.org/packages?view=revision&revision=613740

Status: NEW => RESOLVED
CC: (none) => remi
Resolution: (none) => FIXED
Assignee: bugsquad => loginov_alex

Thank's for Cauldron

Thanks for importing. Unfortunately you did not include all the adoption I made to fit freeplane into mageia.

Esp. you are using the pre-build package, which violated the Magaia Policy.

This any many other improvements can be found at https://github.com/htgoebel/freeplane-mageia:
- building from source
- disabling update checks
- disabling bugreports,
- remove preferences for browser (use xdg-browser)

I would appreciate if you'd include this stuff.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Hello Hartmut, will you send your changes into upstream?

(In reply to Alex Loginov from comment #9)
> Hello Hartmut, will you send your changes into upstream?

Hi Alex, I'm one of the freeplane 1.3 developers. So what exactly do you mean with "send upstream"? These patches are also applied to Debian packages which are prepared by another freeplane developer (Felix).

I suppose Alex means: http://freeplane.sourceforge.net/wiki/index.php/Main_Page
It's great to have your changes in Mageia, but in the end it would be best for all freeplane users if those were the "normal" version of freeplane, as can be found on freeplane's website.

I'm interesting in freeplain. This program by users's opinion is better, then xmind, that's why I chose freeplaine.
I did not know about this bug before and that you are author. Now I know :)

1) - building from source
OK, I'll try, now I know about freeplane-mageia.
2) - disabling update checks
Program have checkbox to disable update check, but If you have patch, then OK, better to disable.
3) - disabling bugreports
Maybe stay? What reason to disable?
4) - remove preferences for browser (use xdg-browser)
Why is this patch not in sources? It's better to have check in code (which platform) and if linux, then to use xdg-browser or to have option in command line, but without patch? What do you think?

If you will support freeplane-mageia, then no problem to package your work. And thank's for good program.

(In reply to Rémi Verschelde from comment #11)

> It's great to have your changes in Mageia, but in the end it would be best
> for all freeplane users if those were the "normal" version of freeplane, as
> can be found on freeplane's website.

Whatever has been accepted for inclusion into upstream already is upstream. But there are some patches left which will not make it into upstream. E.g. upstream needs to be platform-independent and thus have some preferences not relevant (and even confusing) in a Linux-only build.

(In reply to Alex Loginov from comment #12)

Most of my patches are in line with those of Debian. The Debian maintainer is a freeplane developer, too. (And even more "core" than me.)

> 3) - disabling bugreports
> Maybe stay? What reason to disable?

This is a question of Mageia policy. Should bugreports got to Mageia or to the project?

> 4) - remove preferences for browser (use xdg-browser)
> Why is this patch not in sources? It's better to have check in code (which
> platform) and if linux, then to use xdg-browser or to have option in command
> line, but without patch? What do you think?

I assume you are referring to 82_remove_browser_command_prefs_for_other_oses.patch.
This patch will not go into upstream since upstream provides a platform independent package (the "freeplane_bin.xxx.zip"). And for this package there have to be options for all supported paltforms. OTOH Mageia has a Linux-only build, so be should hide these useless options from the user. (Hide, but keep it in the config-file, for the case the user is shaeing ts config over platforms.)

> If you will support freeplane-mageia, then no problem to package your work.

My plan is to maintain the package, sinc I'm using freeplane a lot myself. But
I would prefer maintaining it at some git.magaia.org place.

> And thank's for good program.

You are welcome.

Hartmut, thank you for your answer.
Will you use %{_javadir}/%{name} like http://pkgs.org/fedora-centos-rhel-opensuse-mandriva/olea/freeplane-1.1.3-3.fc15.noarch.rpm.html ? Now you use %{_datadir}/%{name} only.

Are you talking about this (and related)?
/usr/share/freeplane/core/org.freeplane.core

I'll hve to did into this.

BTW: Please note that Freeplane ATM does not build on Mageia 4 (at least here). I'll fix this these days.

See Fedora about *.jar, there are no *.jar in /usr/share/freeplane:

/usr/share/java/freeplane/
/usr/share/java/freeplane/org.freeplane.core/
/usr/share/java/freeplane/org.freeplane.core/META-INF/
/usr/share/java/freeplane/org.freeplane.core/META-INF/MANIFEST.MF
/usr/share/java/freeplane/org.freeplane.core/lib/
/usr/share/java/freeplane/org.freeplane.core/lib/freeplaneeditor.jar
/usr/share/java/freeplane/org.freeplane.core/lib/freeplaneosgi.jar
/usr/share/java/freeplane/org.freeplane.core/lib/freeplaneviewer.jar
/usr/share/java/freeplane/org.freeplane.core/lib/jortho.jar
/usr/share/java/freeplane/org.freeplane.plugin.latex/
/usr/share/java/freeplane/org.freeplane.plugin.latex/META-INF/
/usr/share/java/freeplane/org.freeplane.plugin.latex/META-INF/MANIFEST.MF
/usr/share/java/freeplane/org.freeplane.plugin.latex/lib/
/usr/share/java/freeplane/org.freeplane.plugin.latex/lib/LICENSE
/usr/share/java/freeplane/org.freeplane.plugin.latex/lib/README
/usr/share/java/freeplane/org.freeplane.plugin.latex/lib/plugin.jar
/usr/share/java/freeplane/org.freeplane.plugin.script/
/usr/share/java/freeplane/org.freeplane.plugin.script/META-INF/
/usr/share/java/freeplane/org.freeplane.plugin.script/META-INF/MANIFEST.MF
/usr/share/java/freeplane/org.freeplane.plugin.script/lib/
/usr/share/java/freeplane/org.freeplane.plugin.script/lib/groovy-all-1.5.6-LICENSE.txt
/usr/share/java/freeplane/org.freeplane.plugin.script/lib/plugin.jar
/usr/share/java/freeplane/org.freeplane.plugin.svg/
/usr/share/java/freeplane/org.freeplane.plugin.svg/META-INF/
/usr/share/java/freeplane/org.freeplane.plugin.svg/META-INF/MANIFEST.MF
/usr/share/java/freeplane/org.freeplane.plugin.svg/lib/
/usr/share/java/freeplane/org.freeplane.plugin.svg/lib/plugin.jar

Hi Alex,

I moved the jars to %{_javadir}/%{name}. You can find the updated files at <git@github.com:htgoebel/freeplane-mageia.git>. Version is currently freeplane-1.3.5-alpha_pre06, which is quite stable, though.

I'll try updating to a more recent version these days.

Meanwhile I'm expecting you feedback and or changes. Do not hesitate submitting a pull-request on github

Fixed in freeplane-1.3.11-2.mga5.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED