Before applying with my proposal, i wanted to write to you and getting some advices in this proggress. I started to learn how is packaging at opensuse. What should i read? what should i work on?
We use obs (build.opensuse.org) and osc (cli that works in conjunction with obs). You need an account on obs and you need osc installed. Lots of packaging info in the wiki. I'd start with: http://en.opensuse.org/openSUSE:Build_Service_Tutorial Don't miss: http://en.opensuse.org/openSUSE:Build_Service_Tutorial#A_start_to_end_exampl... As to a hopefully simple project, from my personal to do list, how about updating the specfile for libvshadow in the filesystems repo to be consistent with the specfile from libevt in the devel:libraries:c_c++ repo. Both are from the same upstream dev. I packaged libvshadow first a month or two ago. Libevt is a much improved specfile, so libvshadow needs updating to be consistent with it before it gets pushed to factory. There is also a new upstream release of libvshadow, so the tarball needs a refresh. Questions about this should be on opensuse-packaging. Fyi: if by chance you are interested in suricata, packaging it is something I am working on. Suricata is similar to snort, but a new generation ids/ips project that is not yet in opensuse. I'm busy on other projects for at least the next week or two so you could branch it and libprelude from my from my home project and try to fix any issues then SR them back to me to review. I pushed libprelude to factory last week, but it may need a tweak or two to integrate properly with suricata. I haven't done any suricata testing yet, i'm still trying to get the package to build cleanly in obs. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org