Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=464781 --- Comment #4 from D Haley <mycae@xxxxxxxxx> 2008-10-13 03:45:26 EDT --- Yes, I am aiming to get a scilab package uploaded. I have a (private) basic scilab package all up and running (minus GUI), but I wanted to work out the approval/packaging process. The only thing its missing to get the scilab working in GUI mode is flexdock :) Nicolas: As of scilab 5, I believe matio is not directly required and scilab can (optionally) use its own code (or embedded code) to support these operations. (reference: http://wiki.scilab.org/Dependencies_of_Scilab_5.X). The java guidelines are a bit out of date, and keep talking about using the non sun java components (IcedTea, gcj); it's hard to tell what does and does not apply here. > You have to use macro for the spec file By macro I assume you mean that i should be installing the JNI .so files to %{_libdir}/%{name}? I can update the spec file accordingly. Otherwise if you are referring to the general format of the spec file, the original spec file was generated using vim, as per (my interpretation of) the packaging guidelines. Is something incorrect? Dominik: I read the guidelines a few times, for me the process is still a little fuzzy. I am following the procedure outlined here: http://fedoraproject.org/wiki/PackageMaintainers/Join, and am up to the part " Watch for Feedback" -- How do I fix the FE-NEEDSPONSOR -- It seems a little bit of a chicken and egg problem, I have to submit packages and get approval to get a sponsor, but can't do that until I have a sponsor... ? The guidelines say "When the package is APPROVED by the reviewer, you must separately obtain member sponsorship in order to check in and build your package." -- so shouldn't I be trying to get approval now??? Confused. Thanks for the help -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review