Steffen Nurpmeso <[email protected]> wrote: > Predrag Punosevac <[email protected]> wrote: > |trondd <[email protected]> wrote: > |> Steffen Nurpmeso <[email protected]> wrote: > |>> trondd <[email protected]> wrote: > |>>|Getting a crash with s-nail 14.7.10 as well as master on OpenBSD. When > |>>|changing folders, sometimes there is a segfault. > |>> > |>> Thanks for reporting that! > |>> (And thanks for spending effort and using S-nail on OpenBSD; it > |>> seems the package has no maintainer.) > |> > |> Thank you for taking a look. > |> > |> There is a maintainer listed, but I haven't heard from him \ > |> regarding updating > |> the package. I have heard from a couple of other users \ > |> who are helping to get > |> the port updated. > | > |The OpenBSD S-nail port maintainer is William Yodlowsky and in my > |experience he is very responsive guy. There is nothing wrong with > > That is not my experience, Predrag. I've sent Frantisek Holop, > Matthias Kilian and William Yodlowsky some messages including > a completely prepared update for v14.7.8 at the end of September > (Matthias Kilian took the thread offlist again). >
Frantisek doesn't have commit privilages. Matthias Kilian is one of core port contributors. Any S-nail update will have to be OK by him. I want to belive that William was just very busy not rude to you. Working for Rutgers University can get under your skin. > |OpenBSD port of s-nail. OpenBSD project has a matter of general > > But of course it is: v14.4.5 is terribly buggy. > I really was very disappointed that i wasn't even worth _a_ > response for preparing a complete package update commit-ready. > > |policy porting only stable peaces of software. Many people refer to such > |policy as very conservative. Just a casual look at your S-nail repo > | > |http://sourceforge.net/p/s-nail/code/ci/master/tree/ > | > |give the impression or rapidly developing, unstable, and very volatile > |code base. I also got the same impression by lurking on this mailing > |list. > > That is not how i would say it. :) And what exactly do you mean > with unstable? Give me an example of *how* you can break the > current S-nail codebase as a normal user -- and i'll fix it right > away! (With the sole exception of the well-known memory leaks > which won't work out before the rewrite; ask for more on > interest.) Well and volatile... the opposite of which can be > found on the [heirloom] branch. Right? I will take back my words then. As sign of my sincere appology I will offer to test 14.7*. Let me know if you need the access to the live OpenBSD system. Current was just tagged 5.7 beta in preparation for 1st of May release. > > |I am sure when S-nail code stabilizes in next couple of years William > |will update the port. > > Indeed v14.7.* is the sole story of stabilizing a codebase and > sucking usage corner cases. Hmmmm... at least more or less. > Let's just see what the future brings. > > --steffen We are here for a long ride with you but some of us are more conservative than others. Predrag ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ S-nail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/s-nail-users
