Hello, I have one question. I would like to submit a review request for Guacamole, an HTML5 vnc and rdp client. The software itself is already packaged in separate small libraries and tools for Fedora: http://sourceforge.net/projects/guacamole/files/current/source/ http://guac-dev.org/Fedora%20Install%20Instructions Since all the pieces taken alone are quite useless, should I fill a review request for all the packages in one singular review or should I fill multiple reviews requests, one for each piece?

Ok, thanks, I will do it this way, then.

Regards, --Simone On 10 May 2012 10:32, Ralf Corsepius <rc040203(a)freenet.de&gt; wrote: > > On 05/10/2012 09:35 AM, Simone Caronni wrote: >> >> Hello, >> >> I have one question. I would like to submit a review request for >> Guacamole, an HTML5 vnc and rdp client. >> >> The software itself is already packaged in separate small libraries and >> tools for Fedora: >> >> http://sourceforge.net/projects/guacamole/files/current/source/ >> http://guac-dev.org/Fedora%20Install%20Instructions >> >> Since all the pieces taken alone are quite useless, should I fill a >> review request for all the packages in one singular review or should I >> fill multiple reviews requests, one for each piece? > > > The latter (one package after the other). > > Admitted, this will take time, but one single review for many  packages is > close to being unmanagable. > > Ralf > -- You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). -- packaging mailing list packaging(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging

Added all dependencies, not before clashing mid air while applying them :D The daemon itself needs a client; documentation on how to write it are on Guacamole web site. The Gucamole project provides its one Web Interface; and I have some struggle packaging it. It is made of the following components: guacamole - The main web application, written in Java. guacamole-common - The Java API used by the web application. guacamole-common-js - The JavaScript library used by the web application. guacamole-ext - Common interfaces for extending the main web application. All compile with maven and in the end they are packaged as a war file: http://guac-dev.org/guacamole I've seen many *-js packages in koji, but they all compile with ant; here I need maven. Can somone point me to some examples in Fedora on which I can rely to build this stack?

Quoting Tom Callaway (2012-05-10 16:06:44) > You might want to ask in #fedora-java, those guys have quite a bit of > experience with packaging Java bits with Maven. Yes, and at least one of them occasionally reads this list :-) > On 05/10/2012 08:57 AM, Simone Caronni wrote: > > Added all dependencies, not before clashing mid air while applying them :D > > > > The daemon itself needs a client; documentation on how to write it are > > on Guacamole web site. > > > > The Gucamole project provides its one Web Interface; and I have some > > struggle packaging it. It is made of the following components: > > > > guacamole - The main web application, written in Java. > > guacamole-common - The Java API used by the web application. > > guacamole-common-js - The JavaScript library used by the web application. > > guacamole-ext - Common interfaces for extending the main web application. > > > > All compile with maven and in the end they are packaged as a war file: > > > > http://guac-dev.org/guacamole > > > > I've seen many *-js packages in koji, but they all compile with ant; > > here I need maven. > > Can somone point me to some examples in Fedora on which I can rely to > > build this stack? Well. For simple-ish examples of using Maven you can have a look at apache-commons-io and related commons packages. They should be relatively clean being updated only recently. To build Java stuff with Maven in fedora you have to use a bit modified mvn-rpmbuild script that works in offline mode. Note that all dependencies (even build-deps) will have to be packaged and properly added to BuildRequires, otherwise the packages will not build. Quick glance at the deps seemed to suggest we have them all so you should be OK. I have to say I kind of like this project. Clear licensing, no bundling, no shading. Way to go. You can high-five upstream if you are in touch :-) There is one more issue: We don't have packaging guidelines for java webapps. You might want to have a look into[1] and [2] where we discussed it somewhat. We should get it over with one of these days. I would propose putting the unpacked war file into /usr/share/webapps-java and symlinking dependencies into lib subdir. Seems like the package is self-contained so even "bundling" its parts in war might be OK here. If you've never packaged Java software for Fedora this might be a bit confusing so feel free to stop by #fedora-java where we can help you out in real-time. [1] http://dep.debian.net/deps/dep7/ [2] http://meetbot.fedoraproject.org/fedora-meeting-1/2010-12-08/fedora-meeti... -- Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt; Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc.                               http://cz.redhat.com -- packaging mailing list packaging(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging